As spotted in a previous thread I have in mind another library facing a similar issue: libcurl. In order to both serve newbies and experimented users, the library offers two API: one exposing all possible settings and the other much more simpler with many presets. As a counterside, the simpler one cannot be used in software with concurrent usages.
In order to offer the ability to forbid usage of the Default Data-Context, I feel that the better solution is to extract this part in a dedicated module (let’s call it orekit-helper or orekit-easy). With such change, consumers can enforce the prohibition of this module.
But as Luc said, this is a major change.