Yes, that is exactly the tagging method you should use. The review tag indicates you're talking about review, the vote-to-close tag isolates that to just the Close Votes queue, and the stackoverflow tag would isolate that even further to just the Close Votes queue on Stack Overflow. Plus you still have an extra tag left over.
The size of the Close Votes queue on Stack Overflow is too specific of an issue to warrant a tag. As Martijn points out, the size of the queue is only one thing. Ultimately all of the separate questions are only identifying the size as the reason for wanting some change to the Close Votes queue, which would be the real topic of the question. It makes more sense to have them all under one question identifying the size as the problem, with answers identifying possible [alternate] solutions to that problem. They're already linked by being duplicates, which keeps them grouped together; we don't need a tag to do that.
not giving it a tag looks rather like plain unwillingness to acknowledge a problem of The Queue
That's a bold statement that's completely wrong. Stack Exchange has acknowledged the problem, and a tag is not needed to indicate their acknowledgement of it. There's also a second problem: there's way too many duplicate questions about this issue. We could easily get by with only 1 or 2 questions about the size of the Close Votes review queue, which definitely wouldn't require a tag at all. A lot of them are already closed as duplicates anyways.
You're basically trying to combine all three of the tags I mentioned above into one, very long tag when they don't need to be combined. People keep saying we need a single tag so we can find them all easier - no we don't. They're just as easy to find if they're tagged correctly with the above three tags.