Looks like the Initializer approach would suit your requirement.
The Initializer only processes configuration files that have changed, this is based on their md5 checksum.
If you mean something that can be deserialized right away, yes we have already taken that route for some domains such as ‘idgen’.
However the preferred approach is to provide metadata (or even data in some cases) through CSV files. And each new CSV would require to implement an ad-hoc line processor extending BaseLineProcessor.
We allow the drop-in of MDS packages because it was an easy, quick and convenient way to bring in metadata, but an XML or preferably CSV parser should always be favored.
We are trying to make the so-called ‘openmrs configs’ such as this one manageable by implementors, and that is why we promote the CSV use case.