Can I avoid the 520 bytes push limit for existing Tapscript opcodes?

Let’s assume you want to introduce arbitrary precision into Bitcoin’s scripting language. This requires that operands of any size can be pushed onto the stack.

BIP342 status

Stack Element Size Limitations Both the initial stack and the pushopcode leave an existing limit of up to 520 bytes per stack element.

It also states that the new opcode can avoid the 520-byte push limit

OP_SUCCESSX precedes initial stack and push opcode size checks, so opcodes derived from OP_SUCCESSX, which require stack elements greater than 520 bytes, can increase the limits of soft forks.

The script already has a handful of arithmetic operations OP_ADD and OP_SUB.

Is it accurate to say that these opcodes can only be reused with precision of up to 520 bytes? If you want more precision, you will need to create a new version of these opcodes (OP_ADD_ARB, OP_SUB_ARB)?