I prefer the term "intentional complexity" because that seems to often be what causes the incidental. You say it right there with the part on how certain processes, methodologies, and "build stacks" actually introduce a mix of false simplicity and task complexity mismatch.

Which is how for example client side we end up with people vomiting up 100k of HTML to do 10k's job, 500k of CSS to do 48k or less' job, and megabytes of JavaScript on pages that don't even warrant 48k or less... if any!

And you certainly have it right that some people WANT this stuff to be complex so they can have their L33T bragging rights. I've seen it first hand. Taking the simplest of problems and through ignorance, brute force, and arrogance making them LOOK complex.

Your "under the rug" chart should have a "Solution C" that's half the total code size of "solution A my code" without any library code, with a note "Thanks to understanding how to solve problems". I say this because the majority of projects I've fixed for clients that's basically what happens. It's not like your chart doesn't have the room to fit it.