I am interested to track the progress in "my neck of woods", that is to roughly estimate how many posts in the queue match the filter I selected (FWIW, my current filter is "primarily opinion-based" and according to Shog, recently queue had 6,345 posts that match it).
Taking into account that I may use filter settings for various close reasons and tags, what could be difficulties to show / refresh this kind of stats? Could there be performance or UX or other problems?
Note similar idea was mentioned in an answer in How to make close-review queue less thankless
It might be helpful if you could see how many questions there are in the queue that fit your filtering options.
That way a reviewer might focus on a seldom used tag with a chance of completely emptying the queue for that tag.
Another answer pointing to this is in Fuzzy the number of questions in the close review queue...
Counter proposal: why not show how many questions are awaiting review in my part of the site...
So if I've filtered the queue to java and matlab the number of close votes isn't 92.5k...
My question differs from above in that I am specifically interested to learn about what could prevent this from getting done.