Yes and that's a major issue

> If Mozilla are really serious about fingerprinting then they need to remove <canvas> right now

Ad absurdum is not as great an argument as you think it is

> Fingerprinting cannot be solved by disabling browser features in a standard browser.

It also shouldn't be facilitated by just blindly turning them on without propert mitigation. And proper mitigation is complex

> It can be mitigated by using content blockers

So now you're shifting the responsibility onto the user. Even though it's been shown time and again that users can't really understand all the complexities of modern systems, their capabilities and the far-reaching results of what these systems can and do.