Correct - it is only possible for AT to work with the new op code (but at least only the one is required).
AT can indeed "spend" its inputs as because they are OP_CHECKSTATE scripts such as this:
INPUT:hash160(1xxATxxYptzC5a7p9obc2SLMPS148G2Qxg) OP_CHECKSTATE (original 100)
Thus there is no signature required to be verified with OP_CHECKSTATE only the actual "state" of the AT VM needs to match each peers own calculated state (and outputs that are created by the AT are verified to match the same set of outputs that each peer determined).