It does, by associating the 'negative emotional experience' of reading a manual (aka learning) with so-called "over-featuring", whatever "over" is supposed to mean. Of course reading a manual is unpleasant, for the same reason studying anything is unpleasant - e.g. engineers study advanced calculus (which tends to create a 'negative emotional experience') because it helps them later do useful things like build bridges that don't collapse.
Likewise, studying a user manual (unpleasant learning/studying) helps you later do useful things with the software - it's an investment, that pays off later, once you are able to get more power out of the software. It doesn't mean advanced calculus is "over-featured".
You don't read user guides because it's fun, just like most people don't study advanced calculus for fun. Most people don't study accounting for fun, but studying accounting has huge benefits later if you run a business.
The basics of software should usable by the average user with minimal studying, sure, but there is an inherent point at which you must invest in doing some unpleasant learning if you want to get the full power and return on investment from the software product.