The OP_RETURN outputs don't take that much space so I don't think it's a battle worth fighting. If it was, mining pool operators would pop up offering the opposite stance as a selling point (like Ocean with inscriptions). 

netstatic

bitcoin

Wouldn't it be desireable to limit the number of OP_RETURN opcodes
that can be applied per coinbase transaction to one?

**Problem:** 
In merge mining [transactions such as this][1] there is data that is not 
the [root of the Merkle of this block][2] but from what I gathered it is data 
that references something relevant to another blockchain (merge mining). 
While one may speculate about indirect benefits of merge mining for Bitcoin, 
the data included in the transaction through the second OP_RETURN takes up scarce blockspace. 
This data than will have to be stored by full nodes indefinitely. 

Are there any BIPs that would aim at limiting such a waste of precious blockspace? What might be an unintended consequence of limiting a number of OP_RETURN opcodes per coinbase transaction to one?



[1]: https://mempool.space/tx/fb77494f9929a36c2f81a1bd1d10586e9a541d25d4f782b5d07c871885d3dc36
[2]: https://github.com/bitcoinbook/bitcoinbook/blob/develop/ch06_transactions.adoc#coinbase_transactions