Segregated Witness – How do pre-Segwit nodes interpret transactions containing Taproot OP_CHECKSIGADD?

When a pre-Segwit node encounters a block involving a Segwit transaction, it can verify it and move on to the next block, treating it as an “anyone can spend” transaction.

However, when a transaction with an opcode occurs, 0x6a (Tap route only OP_CHECKSIGADD) They consider this an undefined opcode and thus the transaction and its block are considered invalid. Then they will split or become stranded.

But after reading this it seems like there is a way to handle/avoid the old node. OP_CHECKSIGADD.

What is the mechanism by which the previous node handles the following? 0x6a/OP_CHECKSIGADD Can these opcodes or transactions be viewed as “anyone can spend”?