The config.sup is for settings that users (or any other config.pro files) are not allowed to change in Creo and seems like a perfect place for corporate wide mapkeys to create standard processes/toolsets. In Creo 3 M060 as shown in the attached video, the config.sup will allow MANY mapkeys to exist in a Creo session but not let ANY of the mapkeys from the other config.pro files (e.g. a users config.pro) load into Creo. It would be way more flexible if the other config.pro mapkeys would load into session as well. Where two mapkeys have the same name, always use the config.sup mapkey. General user config.pro files often tend to get tons old settings and mapkeys built up over time if edited from Creo so superseding user mapkeys where a naming conflict exists help admins keep users using the latest and greatest processes/mapkeys as things inevitably change.
Several good ideas were shared in Re: Corporate Mapkeys - Superseding User Mapkeys about how to accomplish this but currently require a lot of monkeying around or restructuring of config setup locations to somehow load the desired corporate mapkeys last. The idea above would make this way easier.