The text you quoted states clearly that "HTTPS content analysis [...] is not acceptable (technically speaking, and from the user's privacy respect)". So it's not me being dense.
It also states that "Despite our disgust for this fact, HTTP has become a de-facto standard transport protocol for many purposes". This means, in other words, that "a lot of people is using what they should not be using", i. e., there are other solutions to that.
Finally, you state that "perhaps you don't understand all the use cases?" Nope, I do, in fact, understand _all_ the use cases. And for all of them, a well-thought combination of network authentication (802.1x + RADIUS), traffic shaping, and maybe limited VPNs are the correct solution, in the correct network layers.
Maybe you can disprove me if you cite one use case (or more than one!) where my last statement is not true (*), or if you can explain to me why it is so.
(*) I will probably show you that you are wrong, and that dot1x is a better and simpler solution. But give your best shot, I don't mind being wrong.