Spamming or including spam in blocks? What do you mean? No one is stopping anyone from making whatever mempool policy they want. Especially now as they're not even removing the filter. Carry on in Core 30 with the same filter if you want. Gossip is going to relay these transactions no matter what your filter says. Now your node won't gossip about it to others so you can reduce how much they are "talked about" between nodes but the network will absolutely always know about them.

"No one wants to censor your transaction, they just want to censor transaction if it's not a certain kind of transaction."

Do you understand the conundrum we have here?

Do whatever you want in your mempool. Don't make the same argument for consensus rules. There is no way to stop "non financial transactions" from being included in a block. I'd argue any consensus tx is a financial tx. They're paying a fee in a currency to a miner. That's financial. You're free to disagree and make your mempool reject whatever you want.

I believe it's a non-issue because the detractors motivations for setting that policy are inconsequential to the results. It doesn't matter if you raise or lower it that's the whole argument.

The argument to eliminate would be precisely because it doesn't do anything in practice with the actual network only to the local nodes Mempool. The reason detractors do not want it and their mental are not performance related. Their motivations are altruistic. Bitcoin is software. Computers don't care about your altruism. Does the filter meaningfully impact node performance or hardware requirements? Does it change the network?

If the answer is no to both, then data carrier filtering is useless code. If it's useless code it should be removed from core, the reference implementation, and if users want to just truly be altruistic they can run a fork or not update and keep using the filter (If it were removed which it isn't...)