I'd say that if you don't want your packets inspected, use encryption and only trust specific certificate authorities.
A regular HTTP GET is meant to be cacheable and meant not to be considered private. If you want private, use SSL and do not encode information in URLs that can be abused by intermediaries.
I realize you consider the attempt to charge upstream providers a fee to ensure high quality throughput extortion, but the fact is, some services utilize 99% of bandwidth.
Take the typical residential ISP, 99% of the upstream bandwidth it purchases likely moves traffic from youtube, youporn, etc. In the remaining 1% are gmail, HN, VOIP, etc.
The natural move would be for the ISP to adjust QoS to favor minimal streaming quality that will prevent customers from defecting to another ISP.
But content providers compete on the basis of content variety, quality, etc., and so their incentive is to maximize quality. If you are 1% more likely to click on an ad after watching porn at 4K, then it's potentially worth it to youporn to serve only 4K quality video since bandwidth is cheaper at scale and highly predictable.
But an ISP is operating at smaller scale. For last mile circuits, bandwidth cost is bound by hardware investments, and so a disproportionate amount of the cost of Youporn's added 1% chance you'll click is borne by the ISP.
So how can the ISP align its own incentives with youporn? Simple, by threatening a QoS that will reduce network load in exchange for a fee that helps share the cost of the additional bits.
So it's not extortion any more than Uber surge pricing is extortion. It helps increase the efficiency of the market process going on by aligning incentives where previously they were less aligned. Strong market incentive exists for ISPs not to overplay their hand, and to date as far as I know this hasn't been a problem.
I agree that last mile monopolies are bad, but the solution isn't to entrench them with top-down regs that hide the problem.