Config in defaultconfigs is ignored when correcting single values in a config file

[Fuzss]

When single config values need to be corrected (think like the config value is a number 1-10, but the user enters an incompatible input like '15', in that case only this single value needs fixing not the whole file),
Forge restores the mod specified built-in default value for that option, but ignores a value that is set in a possibly present default config in 'defaultconfigs'.
The expected behavior would be to first check for a value in a default config from 'defaultconfigs' before falling back to the mod specified built-in default.

Example: An int value allowing a range of 1-10.
The built-in value set by the mod is 5.
A config present in defaultconfigs specifies 7 for that value.
The user enters 15.
-> The value is corrected to 5, not 7 as would be expected.

This isn't really a bug, but more of an oversight with how default configs are designed. Just thinking that logically default configs should serve as the default not just when a config is first created, but also when individual values are restored / corrected.