The asker is not closing the question. They're not closing it unilaterally, they're not closing it with Community's help, they're not casting a binding vote or exercising any special privilege. They are answering a question posed by the system, and the system may close their question based on their response.
I know this seems like splitting hairs, but... It's a pretty important distinction. Losing it opens up a huge, huge can of worms: users expect to be able to undo actions attributed to them, to understand what the system is saying they did. Maybe someday that can will need to be opened; maybe someday we abandon this closing system and move on to something a bit more lightweight where askers do have a lot more say into what happens on their questions. Or maybe we abandon closing for duplicates and go with some other system. But not today.
If you want to reduce confusion, propose an alternative to the tooltip that currently tells the story here. Maybe an alternate description for the close?
This question has been asked before and already has an answer which satisfied the asker's needs. If you have a related question, you can ask it separately.
It looks like the question was "mod closed" as a duplicate against the asker's wishes.
Then every other form of dup-closure looks this way too. Perhaps you could suggest alterations that would make duplicates look less... combative?