the questions I asked them were so far below where they were, that it ANNOYED them to have to answer them...innate frustration of people who work in IT when it comes to trying to communicate a concept to someone who isn't at the level where they can UNDERSTAND said concept...so many people in IT suffer from such severe functional fixedness...
So, what is your conclusion anyway? Sounds to me like, "I understand it, but I can't understand it."
Okay, so you ostensibly started this post because you want to correct the "End Users Are Stupid" concept...then went on to document exactly why it existed. In my experience, if you want to correct the EUAS syndrome, you need to have a clear understanding between the parties involved that 1) some things are better left commanded than explained, and 2) don't take it personally when this happens to you. Unfortunately for sharp techies, they're usually on the sending end of this conversation, and get put in a bad light; equally unfortunately, they are on the sending end so often they have no ability to be on the receiving end. But IMO you don't correct the problem by changing #1--this leads to Dilbertian-scale operational collapse; instead you educate people (both techies and end-users) on #2. Sure, you can spend vast amounts of money, time and labor on helping salve the harsh realities of command-style communication, but it only goes so far before the return diminishes rapidly.