Then it's not so much a cookie consent API we're looking for but an "unwanted cookie" consent API. Issue immediately becomes political, which IMO is why previous attempts at such (Do Not Track header) have failed.

With browsers you can of course default to blacklisting all cookies and add exceptions as you go. I did this privately in Firefox until I was sent to work from home during the pandemic, after which figuring out what cookies I needed to enable to get Teams to work proved too much of a hassle.

It has nothing to do with political consent. It's a matter of providing a user with better UX for cookie management, precisely because "blacklist everything from this domain" is too broad.

It is worse than UX issue - it is a billateral UX really for what both designers ans usere can do tying functions together to "subvert the purpose" in combinatorial explosions.

The political is in trying to limit the options to either party like the Computer Fraud Abuse Act charging someone for entering in every possible phone number into a phone directory. The extreme unlimited (il)logical extreme is "If the user is capable of exploiting several 0 day escalation of priveledge attacks to download all of the credit card information and then delete the website that is on the designers for making a shoddy website" being legal. That would be a pure "no politics" UX system with many obvious and inobvious side effects.

I use Brave + uBlock and get nearly this exact experience. Disconnect and Privacy Badger also work well.

I use uBlock as well, but it doesn't have a convenient interface that allows me to inspect and modify cookie permissions.

What is your workflow when visiting a new site and figuring out what cookies to allow?