Agreed. Setting up blacklists is just whack-a-mole. I'd be more interested in detection of actual fingerprinting techniques, such as system font enumeration using canvas, or WebGL GPU fingerprinting. It would be technically possible to detect the creation of WebGL or canvas contexts that aren't actually rendered in the layout and prevent data gathered from those contexts from being sent in any XHR payload. I'm sure that's a lot of work.

Maybe it would be better to find the worst offending JS APIs and demand a user consent step similar to webcam or notifications in order for the scripts to run at all.