ID 545907 - OCIO callbacks do not run if Nuke is launched with a Python argument

Problem summary:
OCIO callbacks do not run if Nuke is launched with a Python argument
 
Customer reported version:
Nuke 14.0v2
 
Customer reported platform:
Windows 10
 
Steps to reproduce:
1) Create a simple Python file that contains print("Hello World"), and save it as "hello.py"
2) Open a Command Prompt or Terminal and launch Nuke with the Python file as an argument, like the example below:
"C:\Program Files\Nuke14.0v5\Nuke14.0.exe" C:\path\to\hello.py
3) Once Nuke is open, navigate to Edit > Project Settings... > Color, and switch the color management from Nuke to OCIO
4) Create a Read node and select an 8-bit image file, like a PNG
5) Observe how the Read node's Input Transform does not match the default LUT for that file type, pictured below:

 
Expected behavior:
OCIO callbacks should function even if Nuke is launched with a Python script to execute. 
 
Actual behavior:
Providing Nuke with a Python script to run at launch prevents OCIO callbacks from working.
 
Workaround:
No known workaround at this time.
 
Reproduced by Support in:
Nuke 14.0v5 - Windows 10, CentOS 7
Nuke 13.0v1 - Windows 10
Nuke 12.0v1 - Windows 10
Nuke 11.0v1 - Windows 10
Nuke 10.0v1 - Windows 10, CentOS 7
 
Earliest version tested:
Nuke 10.0v1 - This issue appears to be in all tested versions of the product