Uniden command codes are very similar model to model in many cases. I don't know enough about programming to know the details but there is a radio identifier as part of the packet, I assume ProScan ignores it during virtual control. Other software and devices seems more particular.
We had this issue in the creation of the RH96 converter for the P2 series. Ric Plummer's solution was a device that converted the 996P2's radio ID to an XT so that the RH would be fooled and connect to the device. Since the rest of the control codes matched it worked.
In my situation I use a mix of BCD325P2, BCT15, BCT15X, BCD996XT and BCD996P2's, all of which will work when any of those radios are selected as the radio type in ProScan. I haven't tried it with the BC125AT but now will assume it too will work.
With all that said, there might be situations (such as actual programming vs. virtual control) and features that might break the continuity so if your radio is listed in the radio types it is better to select it. I don't think the 125 is listed (yet) but if there is a demand I am sure Bob will add it.