ID 523799 - The File I/O SDK fails to implement ARRI Alexa 35 MXF files when using an alternate directory to source the plug-in

Problem summary
The File I/O SDK fails to implement ARRI Alexa 35 MXF files when using an alternate directory to source the plug-in.

Customer reported version
Nuke 13.2v5

Customer reported platform
Windows 10

Steps to reproduce
1) Download ARRIRAW Alexa 35 MXF footage. Example clips: https://webgate.io/directlink/85f567510b896511/folder/680412
2) Download and extract the File I/O plug-in for Nuke 13.2 here: https://www.foundry.com/products/nuke/download/sdk
3) Place the File I/O plug-in files into a temporary directory. EX: C:/Temp
4) Create or add an init.py to the .nuke directory with the following script:

import nukeif nuke.NUKE_VERSION_MAJOR==13 and nuke.NUKE_VERSION_MINOR==2:    nuke.pluginAddPath('some/path/FileIOv4_132/)

5) Launch Nuke and add a Read node, importing the Alexa 35 clip.
6) Open the Properties bin of the Read node and view the bottom of the bin for the plug-in information.

Expected behavior
The FileIO plug-in should allow Alexa 35 footage to be read in from an alternate directory as needed.

Actual behavior
The Alexa 35 MXF clips are not being accessed by the FileIO plug-in when the files are stored in an different folder than the main .nuke directory.

NOTE: The Alexa 35 ProRes MXF files appear with the alternative directory without issue.

Workaround
Using a wrapper script to launch Nuke with the NUKE_PATH environment variable pointed to the FileIO plug-in directory allows Nuke to view the ARRI Alexa 35 footage with the plug-in. An example wrapper script can be used as follows:

set NUKE_PATH=C:/Temp/FileIO132/"C:\Program Files\Nuke13.2v5\Nuke13.2.exe"

Reproduced by Support in:
Nuke 13.2v5 - Windows 10
Nuke 13.2v1 - Windows 10

Earliest version tested
Nuke 13.2v1 - This feature did not exist before this version (Alexa 35 supported in 13.2v1)

We're sorry to hear that

Please tell us why