How about a domain.tld/.well-known/cookies.txt file that contains a description about each cookie-key and then let the browser provide the UI for displaying that information and being configurable on which individual cookies to store for how long? (and for example discard all cookies that are not described in the cookies.txt file)
That won't work. The cookie banners are annoying and tricky on purpose.
As a legal professor said (paraphrased): it was amazing to see an entire industry come together to undermine legislation.
Why are websites required to inform a user about data tracking and required to ask for consent in a custom implemented, not-machine-readable dialog/poup. The user can not even check if the tracking is actually disabled once they clicked "decline" or "only accept technical required cookies".
Why not require websites to provide that information on a per-file/per-cookie/per-localstorage-key level. Then browser could block all js-files/cookies/storage-entries that have now proper description included (eg, in an http-header for files, or a robots.txt-like cooies.txt file, or as standardized comment at the top of a js file).
Currently there are extension like no-script taht block everything, but how about allowing/requirig site-owners to annotate files with tracking meta data in order to be unblocked?