ID 603155 - The Viewer can display incorrect results after an OCIO config is reloaded

Follow

Problem summary:
The Viewer can display incorrect results after an OCIO config is reloaded 
 
This issue is known to affect the following configs, but may impact custom configs as well:
fn-nuke_cg-config-v1.0.0_aces-v1.3_ocio-v2.1fn-nuke_studio-config-v1.0.0_aces-v1.3_ocio-v2.1 cg-config-v1.0.0_aces-v1.3_ocio-v2.1studio-config-v1.0.0_aces-v1.3_ocio-v2.1 
 
Customer reported version:
Nuke 15.2v1
 
Customer reported platform:
Windows 10
 
Steps to reproduce:
1) Launch Nuke and navigate to Edit > Project Settings...
2) Switch to the Color tab, and set the color management to OCIO 
3) Then, set the OCIO config to fn-nuke_studio-config-v1.0.0_aces-v1.3_ocio-v2.1
4) Create a CheckerBoard node in the Node Graph, and View it
5) Change the Viewer Process from ACES 1.0 - SDR Video (sRGB - Display) to ACES 1.0 - SDR Cinema (D60 sim on DCI) (P3-DCI - Display)
6) In the Project Settings, press the Reload Config button
7) Observe how the Viewer's output changes, despite ACES 1.0 - SDR Cinema (D60 sim on DCI) (P3-DCI - Display) still being selected:

 
Expected behavior:
The Viewer should not produce different results when reloading an unchanged OCIO config.
 
Actual behavior:
When an OCIO config is reloaded, the Viewer may no longer display the correct results. This seems to occur for most of the color transforms in the (fn-nuke)cg-config and (fn-nuke)studio-config OCIO configs.
 
Workaround:
Besides completely deleting the Viewer node and creating a new Viewer, there is no known workaround at this time.
 
Reproduced by Support in:
Nuke 16.0v4 - Windows 11, macOS 14 Sonoma
Nuke 15.0v1 - Windows 11
Nuke 14.0v1 - Windows 11, macOS 14 Sonoma
 
Earliest version tested:
Nuke 14.0v1 - This feature (the ACES Studio/CG configs included with Nuke) did not exist before this version

    We're sorry to hear that

    Please tell us why