There should not be any issues synchronizing changes involving composed attributes from a PingDirectory Server instance to some other type of endpoint. Changes that create or update composed attributes should be written to the LDAP changelog, just like changes to regular attributes.
Synchronization to a PingDirectory Server configured with one or more composed attribute plugin instances may be more problematic. In particular, it may not be possible to a composed attribute type if the plugin that generates values for that attribute is configured to prohibit external clients from altering values of that attribute.
If the PingDirectory Server is used as a sync destination in an environment in which some attribute values may need to be composed, then it may be desirable to compose those values in the Synchronization Server using a constructed attribute mapping rather than attempting to generate them in the Directory Server with the composed attribute plugin.