One reasonable option could be to re-use Kryo AND register custom serializers that instantiate the base constructor without using reflection and use the to and from binary methods that are already defined.

Another option would be the have persistenceutils just recall our own SPI service provider that provides a mapping of unique identifiers to serializers (where the serializer is primarily responsible for instantiating the base constructor and calling to/from binary), and when not found it can use the current reflection approach. This approach could minimize the backwards compatibility issues with refactoring package names.