AUDIO/0158 in a 15-1994 is Sony devices 16 and 13. That codes is not in the 2116.
AUDIO/1058 in a 2116 is multiple Sony devices. It is a "2 byte" protocol for which you need JP1 in order to do advanced codes.
MISC/0159 in a 2116 is Sony devices 12 and 13. Any advanced code that corresponds to an odd hex cmd in AUDIO/0158 should have the same EFC in MISC/0159.
TAPE/0243 in a 2116 is Sony devices 16 and 0. Any advanced code that corresponds to an even hex cmd in AUDIO/0158 should have the same EFC in TAPE/0243.
EFC 114 corresponds to hex cmd 14 (which is even). For other EFC to hex cmd translation, use the EFC calculator on the tools menu of IR.EXE (you can download an use IR for that even if you don't have a JP1 cable).

To assign this key move without JP1, you rely on the fact that key moves retain their source setup code even after you change the setup code of the device button used to define them so:
1) Reassign the device button to be TAPE/0243.
2) Test EFC 114 (in case I got some detail wrong).
3) Set up a key move for EFC 114.
4) Reassign the device button back to be AUDIO/1058.

With JP1, that process is much simpler.

With JP1 you could also assign the 2 byte key move, which just wastes a byte vs. using TAPE/0243, but would be useful if you didn't know about TAPE/0243. You use the EFC calculator to translate the EFC (114) to a hex cmd (14), and you use the EFC calculator to translate the device number to a hex cmd. For Sony, you type the device number (16) into the LSB field and read the hex cmd (08) from Hex Command field. Then you select the Hex Cmd option in the dialog for adding a key move and type in the 2 byte hex cmd (14 08).

I don't have a 2116. I haven't tested ANY of the above. Good Luck.