Going over them one final time with advice from @roelh. I've updated them to show which are 16 bit and which are 8 bit. I've removed the XNR instruction, although I thought it was a good way to set a byte to FF, like the status register. Used the free'd up codes to add the opposite jump's JNC, JNZ, JNM, and some XY stack addressing to the ADD and SUB commands.
Going through this I'm questioning how I have the XY stack instructions currently. If it is being used as a stack that grows down in memory (starting at a high address and growing toward 0000h) then any time it is the destination it should be pre decremented. This way it will move to it's new address then store, then it will hold the address of the last byte it stored. When reading from the stack, or popping, it should post increment, so that it moves to the location where the next byte will be stored, and it will always be pointing to valid data (unless you hit bottom of the stack).
Is there something wrong with my thinking? If not then I have the increment and decrements of my XY stack instructions wrong.
Since I have a dedicated stack pointer (SP), should the XY stack grow towards FFFFh ? This way both stacks can share the same memory space. If so, using the above logic, store instructions to the XY stack should be pre incremented, and reads or pops from the stack should be post decremented. If so then my instructions are still wrong.
Is there anything I am missing?