You are incorrectly attributing the blockchain's transaction patterns to Bitcoin Core's default mempool policies. They think the blockchain 'reflects' these filters because the filters are actively preventing bad transactions from being included.
This is backwards causation. The mempool policies are purely local settings that only affect what transactions your individual node will relay or store in its mempool - they don't control what gets mined into blocks. Miners can set these filters to whatever they want, or ignore them entirely.
The real reason the blockchain resembles the default policy settings is much simpler: most people naturally create valid, reasonable transactions anyway. The blockchain looks 'clean' not because the filters are working to keep it clean, but because there wasn't much junk to filter out in the first place. The filters are largely redundant - they're rejecting transactions that most users wouldn't create anyway.
You have it the wrong way round.

They don't do anything to the network. Prove me wrong.
Where are op return codes >80?
There are very few because they don't make any sense financially. Do you want me to submit one now to prove you wrong send me 5K and I will just like I started this conversation with.
So why remove the limit and configurability if it doesn't matter?
Because it doesn't matter... That's the whole point. We don't need code in the code base that doesn't do anything.
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed