Emulation would be easiest with JSON types, however there is no interface to distinguish between printing/reading a type as a JSON string or XML string. StringRepresentableType is too ambiguous in which way it's supposed to be used, and it can't be relied on for either as it's currently implemented.
And there is currently no method of passing persistence-context-specific property values to the type contributor, so controlling that choice through a setting would be impossible while it's a standalone plugin.

However, emulation would imply using `setString`, rather than `setArray` and not using any part of this as it is with the current PR.

I'll post an update to the PR detailing what I think needs more work, so as not to lose track.