Paying to a fake key or hash cannot be controlled by policy, no matter how aggressive you get. You might say this is expensive, but not by much more than embedding data in fake p2ms (which is controllable by policy). Is there a point to forcing people into the worst class of data embedding in terms of node resource consumption?
Discussion
Because Bitcoin is not a distributed data storage service. It is a monetary network for monetary transactions. Paying a fake key IS a financial transaction at the end of the day. If I pay a shell company for items that I never receive I still paid it.
Preventing spam is not the point anyway, it is this strange reframing of "We are taking away a config option which gives you more freedom"
This is blatantly false and could only serve to make spam easier to do. That is the contention, nothing else.
I don't care if spam actually increases or decreases. I want people to FREELY choose to enable spam or disable it. Everything else is sophistry.