I do understand your point of view. I run Bitcoin Knots node with the default 42 Bytes OP_RETURN. I understand that monetary transactions are narrower use case in comparison to email or speech. But in my opinion making the exact limits for all valid use cases is nearly impossible. >with the minimum set of operations are allowed In this case what exactly are the minimum set of operations? Look at Taproot and SegWit hacks. They use OP_FALSE and OP_IF This is what Luke is saying about the issue. "Since the end of 2022, however, attackers have found a way to bypass this limit by obfuscating their spam inside OP_FALSE OP_IF patterns instead of using the standardized OP_RETURN. This remains under active exploitation to a degree very harmful to Bitcoin even today." from here

GitHub

Witness scripts being abused to bypass datacarriersize limit (CVE-2023-50428) · Issue #29187 · bitcoin/bitcoin

The datacarriersize policy option is meant to limit the size of extra data allowed in transactions for relaying and mining. Since the end of 2022, ...