Loading configuration and re-saving it immediately should not result in any changes. Put another way, if the all the runtime dependencies of the configuration are satisfied (i.e it works), then regardless of any additional modules being enabled, the configuration should not change. An interesting case of configuration chainging unexpectedly was discovered in a bug with the filter module. The filter module was adding all the disabled text filters to every filter format configuration entity. This meant enabling any module that provides text filters would change existing filter formats if they were re-saved with no configuration changes. This could cause a site owner to think they need to synchronise configuration even when nothing on the site had changed, and would give anyone reviewing a deployment more to review than necessary.