ID 549833 - Nuke Studio can display an incorrect OCIO config Version when the OCIO environment variable is used

Problem summary:
Nuke Studio can display an incorrect OCIO config Version when the OCIO environment variable is used
 
Customer reported version:
Nuke Studio 14.0v5
 
Customer reported platform:
N/A
 
Steps to reproduce:
1) Open a Command Prompt/Terminal and run the following command to set the OCIO environment variable:

set OCIO=C:\Program Files\Nuke14.0v5\plugins\OCIOConfigs\configs\studio-config-v1.0.0_aces-v1.3_ocio-v2.1.ocio

2) In the the same Command Prompt/Terminal, launch Nuke Studio with this command, or similar:

"C:\Program Files\Nuke14.0v5\Nuke14.0.exe" --studio

3) Navigate to Project > Edit Settings > Color Management and observe the displayed OCIO config Version, pictured below:

 
Expected behavior:
When using the OCIO environment variable to specify a config file, Nuke Studio's Project Settings should display the correct OCIO config Version.  
 
Actual behavior:
Nuke Studio's OCIO config Version displays "v1.0" where it should be "v2.1" for this particular config. However, while inside the Nuke Studio session, Nuke's OCIO config Version (accessible from Edit > Project Settings...) displays the correct value:

 
Workaround:
No known workaround at this time
 
Reproduced by Support in:
Nuke Studio 14.0v5 - Windows 10, CentOS 7
Nuke Studio 14.0v1 - Windows 10, CentOS 7
 
Earliest version tested:
Nuke 14.0v1 - This feature (support for OCIO v2 configs) did not exist before this version