It’s not.
> now every site needs to get your consent
No it doesn’t. You’ve been conned. Look at what they’re trying to get your consent for, and you will find that you would almost always prefer that they not do it.
It is if you are linking to a site hosted in the US because if the browser preloads it you send your IP to a US server which is not allowed.
The referenced lawsuit used a <link> tag, but an <a> tag can result it a browser sending a request too.
>No it doesn’t
It does if they want to follow the law.
>and you will find that you would almost always prefer that they not do it
I don't mind companies having analytics using data they have collected from me.
> It does if they want to flow the law.
No, they can just not do it. Simplifying very slightly: they’re trying to get your consent precisely because they don’t have to do it, therefore they’re not allowed to without consent. I would also note that the sort of consent they solicit on public websites is practically always for storing stuff on your machine (ePD, from 2002) rather than for processing (GDPR, from 2016). But I lack energy to get further involved in this aspect; suffice it to say that their tracking is basically never in your interests at all, and routinely not even in their direct interests.
Which is what browsers can do for link tags. Some browser scan for links on pages and speculatively load them so that if you were to click on them it loads instantly. You as the website author can't prevent this functionality.
>No, they can just not do it
But they want to do it and may have business reasons to do it.
>their tracking is basically never in your interests at all
The tracking likely either improves the service based off analytics which is in my interest or it makes ads more relevant which makes the site more financially viable which is also in my interest if I am gaining value from that site.
Anything like that is user (the browser acting as their agent). You’re obviously not responsible for that. You didn’t ask it to do that automatically, unlike <link rel="stylesheet"> and <script> and the likes.
Things like <link rel="stylesheet">, <script> and <img> are subresources: instructions to the browser to fetch and use the specified resource, so that the page can be rendered properly. As you say, the user agent can choose to ignore these instructions (and text-mode browsers will generally ignore all three of these subresource types), but the page will probably be materially compromised, and the developer placed the subresource there with the expectation that it will be loaded.
A hyperlink is a reference to another page altogether, that it’s up to the user to access if they choose to. It’s not a subresource.
I don't understand why it wasn't immediately obvious to browser vendors that this was going to be how web developers responded to GDPR; and that the browser vendors could/should get ahead of this degradation of the quality of the web-browsing experience by giving the user a way to do GDPR consent at the browser-chrome level by e.g. ticking a box in the browser preferences that will set a request header. (It didn't work for Do Not Track, but Do Not Track is a "request" to a malicious adversary; while "I consent to cookies, so stop prompting me" isn't.)
I can only guess that browser vendors don't like GDPR, and so are avoiding implementing such a GDPR quality-of-life feature in order to ensure that users get just as annoyed by the cookie prompts as they should be, and eventually demand the law be changed.