Disagree.
In the early 00s, spam was killing email. I was getting thousands of spams per minute to my personal email domain (same one I still have and have had since the mid 90s). It was real bad back then.
Doing aggressive sanity checking on incoming email back then was problematic since nearly all legitimate senders also has badly misconfigured email servers.
Those days are gone. Legitimate senders have well-configured email now, one can do a lot of sanity checking on the SMTP connection and that alone cuts out most of the would-be spam before it is ever sent and none of the real email is impacted.
Sprinkle a bit of bayesian filtering on what remains and spam is mostly a non-issue anymore.
So what it the problem these days? Part of it is a legacy cultural problem. A lot of email admins wear so many scars from the early 00s that they still operate on a mental model that they are willing to throw away a lot of legitimate email just to prevent even one in a million spam to go through. That's highly counterproductive and causes a lot of harm to interoperability.
The other big factor of course is that the very deep pocket email providers (gmail, microsoft) have a strong vested interest in strenghtening their monopoly even further so they are happy to go along anything that decreases interoperability.
That all said, I strongly encourage everyone who can to run their own email. Interoperability can only be saved by exercising it as much as possible. And it still works fine despite the naysayers. I've been running my email infrastructure for a long time and have no deliverability problems anywhere that I've run into.