Describe the bug
Seems like there is an issue where in forge 47.2.1. the config file is incorrectly registered/read, causing it to reset the config files if they are modified.

To Reproduce
Steps to reproduce the behavior:

1. Modify the cuffed-common.toml file (in our case, we were tweaking the interrupt phase speed, to be less frame-perfect)
2. Launch Minecraft
3. Load a world
4. when the config file is loaded, it creates a "incorrect key" error, and the config file is replaced with the default.

Expected behavior
Obviously the Config file should not be re-set when loading Minecraft. As that prevents it form being configured

Additional context
From what we have been able to track down, this is caused by some sort of change in how forge registers/reads the config. We have been trying to track down the issue for about 2 weeks now, and this is the major brick wall where we can't do anything more on our end.