I imported your Hex into IRScope, and it reports that the working code is OrteckMCE device 21, function (OBC) 32. It also notes that the end frame is missing. Reading DecodeIR.html (v2.43 is released), we see that OrtekMCE is designed to send 3 types of frames with minor differences. A frame with P=1 is sent when the button is first pressed, P=2 while the button is held down, and P=3 when the button is released. However, most IR gear can only send two types of frames, and that is true of Pronto Hex. So the working code has the start frame and the middle frame.

The unsuccessful learns are all device 21, OBC 46. As you noticed, the code is half length of the working one, and that's because only the start frame was learned. So I used IrMaster to render and export Pronto Hex for OBC 46:
0000 006B 000C 000D 004A 0025 0025 0025 0025 0025 0025 0013 0013 0013 0013 0025 0013 0013 0013 0013 0025 0025 0025 0025 0025 0025 0013 073D 004A 0025 0025 0025 0025 0025 0013 0013 0025 0013 0013 0025 0013 0013 0013 0013 0025 0025 0013 0013 0013 0013 0025 0025 0013 073D

I think you should be able to replicate this process for all buttons: learn the button, import into IRScope, put the resulting decode into IrMaster, and finally put the rendered Pronto Hex into USB-UIRT.