OP_RETURN has practical uses too. Coinjoin transactions are valid transactions, but limiting OP_RETURN filters them. Imagine if the whole network imposed the same limit as Knots, then no coinjoin transaction would have been mined. Not all the applications of data transfer are limited to storing images or data.
Apart from OP_RETURN, BIP444 blocks OP_IF, which is used in nostr:nprofile1qyt8wumn8ghj7cnfw33k76twv4ezuum0vd5kzmqpzpmhxue69uhkummnw3ezuamfdejsqgxv43pk4mqurmp2u522mc9cvn3n0vzv6vxvy8zs6ulq46cdf7khz53utk7y . It's a valid use-case which enables inheritance planning on Bitcoin. The choices made in BIP444 are not limited to OP_RETURN and those choices are detrimental. It goes against the principle of "Don't fuck with people's money".
