ID 536641 - OCIO config files stored in ~/.nuke/OCIOConfigs/configs are disconnected and not found when Nuke is relaunched

Problem summary:
OCIO config files stored in ~/.nuke/OCIOConfigs/configs are disconnected and not found when Nuke is relaunched
 
Customer reported version:
Nuke 14.0v3
 
Customer reported platform:
macOS N/A
 
Steps to reproduce:
1) Open the Nuke installation directory and copy the /plugins/OCIOConfigs/configs/nuke-default/config.ocio file.
2) Paste the file into the ~/.nuke/OCIOConfigs/configs directory and rename it "dotnuke_config.ocio".
3) Launch Nuke and open the Preferences with Edit > Preferences...
4) In the Color Management section, change the Default OCIO Config to the dotnuke_config file: 5) Click OK to save the Preferences, and close Nuke (saving the untitled file is not necessary).
6) Launch Nuke again and observe the Terminal output, "Warning - invalid OpenColorIO config file <path> specified!": 7) Navigate back to Edit > Preferences... > Project Defaults > Color Management, and observe that the dotnuke_config is no longer selected, but is still an option. Expected behavior:
Nuke should retain the Preferences between sessions and be able to locate config files consistently.
 
Actual behavior:
Nuke attempts to locate the config file from the Nuke installation directory instead of from the ~/.nuke/OCIOConfigs/configs path saved in the uistate.ini file.  
Workaround:
Setting the Default OCIO Config to custom and selecting the desired config file seems to work without issue, pictured below: Earliest version tested:
Nuke 14.0v2 - This issue doesn't appear in this version and has regressed.
Additionally, this feature (loading OCIO configs from ~/.nuke/OCIOConfigs/configs) did not exist before Nuke 14.0v1.