Suppose you, an experienced carpenter, were building a house with a junior carpenter on your team. Now imagine the junior carpenter one day asks you how to cut balsa wood. What would you do first? You would ask him why, seeing as that kind of wood is rarely used when building a house. Then suppose it emerges that the client told him to use it for a support column in the living room because its texture is so nice. That of course isn't possible - a support column made from Balsa couldn't carry the necessary weight and break.
If you hadn't asked why, that might have never emerged and the junior carpenter would have made the column out of the wrong material!
In at least 90% of cases, questioning the question is the right thing to do, because the fundamental premise of the question is flawed and there are better solutions to whatever the user wants to do. (See also What is the XY problem?) Ideally, the asker walks away enlightened, having learned a much better approach to the problem.
I agree the community (myself included) is sometimes a bit too zealous in this, and sometimes a perfectly legitimate request gets buried under a heap of "Why do you want to do this? This is not the right way to do this. Tell us what you want to do" comments.
However, usually, unless what one is trying to do is really, really stupid, politely explaining that one wants to do things this way no matter whether it's ideal or not, will make people shut up and answers come in. In this situation, it's the asker's job to remain polite and make their case, even though technically, they have been wronged by the community. It's unfair, but that's life for ya :)
Maybe you can show some real-world examples where this didn't work out? I'm sure you'll get some feedback on whether people were overzealous, or whether there were such serious problems with the OP's approach that it was a good thing no answers were given.