Yeah, literally no way to stop tracking. Suppose I have an apache module (or the equivalent in some modern http server) that's (a) injecting the necessary code

Yeah, literally no way to stop tracking. Suppose I have an apache module (or the equivalent in some modern http server) that's (a) injecting the necessary code (b) forwarding the traffic information to my nefarious third-party tracking provider. Or, heck, just a third-party solution that consumes my apache logs. It's doing all of this without using the browser itself as a middleman, like the clumsy CNAME masking discussed in the linked Github discussion. This could never be stopped client-side since one's web browser would have no say. Only reason this isn't more widespread already is because a lot of web properties don't have full control over their shared hosting environments. First-party ads are theoretically kinda sorta maybe blockable via various levels of heuristics, which of course adblockers are already doing to various extents today. But as far as preventing your information from being forwarded behind the scenes, there's no technical solution. Legislation is the only hope to curb it.