Hey,
So from what i've gathered, not all MIB files are active by default. Some MIBs are disabled as they may cover areas which are not of general use. The ENTITY-MIB file is not only extremely large, but also covers details most CMDBs won't require (component details like fans, sensors etc.).
Overall the main reason for some of the MIBs being disabled is that they can cause some performance issues with little to no use. In your case, feel free to check what the specific MIB file will cover and if you need that information in addition to the data retrieved by more specific or high-level MIBs.
If you need that data to be present, activate the MIB file and see what the impact is (on a lower environment). My assumption is, that these files aren't used in any ootb patterns, so activating it probably has no impact to the overall discovery scope, but may have impact to the performance.
Hope this helps.
Regards
Fabian
