Hello,
First I want to be clear that JMS is not a protocol. JMS is a standard messaging API that is used to send messages over many different protocols.
Solace JMS uses SMF (the Solace Messaging Format) protocol. So do all of the native Solace APIs you mention. So there is in effect no protocol translation occurring. The native APIs expose some features of the SMF protocol that are not available in JMS, or only available through Solace extensions, which are non-standard by definition. In general these are not commonly used and there is no issue interoperating between APIs.
Apache QPID JMS uses AMQP as the protocol. In this case there is protocol translation occurring in the broker to/from SMF. A great deal of work has gone into making this translation seamless in both directions, especially for JMS APIs which do not have access to all the features of either AMQP or SMF.
Regards,
Ragnar