This information should be exposed via ModuleEffectiveStatement. Note that FeatureEffectiveStatementNamespace should only be exposing features that are supported, rather than all features present in the model. Each ModuleEffectiveStatement should also export the deviations which have been applied to the module.

Preliminary patch: https://git.opendaylight.org/gerrit/69209

This requires modifications to the parser API, so that the implementation/import constraints are taken into account as as what deviations to apply, so that we do not automatically apply deviations and do not process instantiation statements.

StatementDefinition needs to grow a new method, which will identify whether a statement defines a data definition node (and therefore should be ignored in the import-only case).

Is there an outlook on when this would be available?

Having this would help us in reusing e.g. groupings from some YANG modules without actually marking support for those modules, for which we typically now copy those groupings over.

I cannot commit to anything, as this keeps being pushed out by other priorities.

A contribution or a contract would help landing this in a predictable timeline