Saying that might make you feel better about yourself, but it is still no argument for the efficacy of the OP_RETURN cap.
Discussion
You stated the efficacy yourself: "Knots may not recognize some transactions because its mempool rejected them due to default policy." That's the upside, the reason I'm running knots. I recognize the downsides but think the upside is worth it.
Having a latency in syncing with the network and losing your edge to other miners is not an upside.
Right that's a downside. As I said I recognize the downsides. The upside is that transactions that don't follow the default policy are rejected. That's the efficacy of the OP_RETURN cap. I want certain transactions to be rejected from my mempool, the cap does that with great efficacy as you stated yourself.
I did not say that. It rejects them from your own mempool but once they are mined, you have to retrieve it from other nodes that know that transaction.