When we say “the cap is X,” we’re talking about the consensus block-size limit—nothing else. Un-capping OP_RETURN makes it normal for every block to slam into that limit with random data, and once that feels routine, the most “logical” follow-up from Core is to raise the block size again. Meanwhile, the most “logical” move from alternative node software will be to clap back by filtering off-curve fake pub-key blobs—because if we’re playing Whac-A-Mole, we might as well bring a bigger mallet.