[Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?

The discussion on the Bitcoin-dev mailing list revolves around the congestion of the Bitcoin mempool due to the high volume of side projects such as BRC-20, which is pricing out real Bitcoin transactions. Ali Sherief suggests a solution to curtail the unintended consequences of BIP 342 by introducing a consensus rule change or enforcing censorship at the node level to prune non-standard Taproot transactions. Michael Folkson argues that rejecting any transaction where the fee is higher than the sum of the outputs would impinge on a valid use case and require a consensus rule change. Erik Aronesty proposes an easier solution to reject such transactions. The debate continues about the purpose of paying an on-chain transaction fee greater than the amount receiving could possibly serve and the benefits of facilitating dust transactions.