Yes and if you configure your Bitcoin Core to have more than 21 million coins you will not be in consensus with anyone else running a Bitcoin Core node and instead be running a shitcoin node.
Discussion
please show me the line the bitcoind parameter where you can make Bitcoin Core have more than 21 million coins.
you can however decide to decide to change the OP_RETURN sizing with "-datacarriersize"
what you're talking about is creating a fork of the the Bitcoin network.
we are talking about a configuration line item here. these are all very, very, different.
I understand the difference just fine. You can configure your code to filter these transactions all you want but they are legitimate transactions and whether you censor them or not, they will be able validated by nodes unless you create a fork. That's my point. The only way to stop them, which is what Luke suggests as he says they're exploitative, is to hard fork or uasf.