I'm familiar with these points. I am not sure that fixing the current instantiation of inscriptions via OP_FALSE OP_IF checks would be enough though. There are ways ways to embed arbitrary data and it seems to be the only option to remove the possibility entirely is to only allow a set of well known transaction types, much more restrictive than what Core currently categorizes as "standard".
And here is the key.
Core ALLOWED the spam that currently abuses Bitcoin by not fixing it with Luke's PR. So Citrea abusing Bitcoin is direct effect of malicious Core devs actions.
"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, 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.
A straightforward way to address this is to simply fix the bug (#28408), but that was (inappropriately) closed due to social attacks."
https://github.com/bitcoin/bitcoin/pull/28408
Discussion
They are already fixed in Bitcoin Knots. And Knots is working fine.
All legitimate transactions and use cases can be tested but as for monetary transactions that transfer value, its all fine.
Restrictions is when someone takes away your options - deprecations first, removal second.
One thing to notice is that Bitcoin Knots gives you the FREEDOM to put whatever value in OP_RETURN you like. Think about that too.