ID 159696 - Workspaces in a custom location aren't available to Nuke unless HIERO_PLUGIN_PATH is set

Problem summary
Workspaces in a custom location aren't available to Nuke unless HIERO_PLUGIN_PATH is set

Customer reported version
nuke.13.1v2

Customer reported platform
windows10

Steps to reproduce

1) In Nuke, create a custom Workspace and save it in a non-Nuke directory, then quit Nuke.
2) Launch a Command Prompt or Terminal and add a path to the custom Workspace to NUKE_PATH environment variable.
    - EX: set NUKE_PATH= C:\Temp\Workspaces
3) Launch Nuke and verify the Workspaces available.

Expected behavior
The custom workspaces should be available in Nuke after adding the directory to the NUKE_PATH.

Actual behavior
Nuke does not pickup the workspaces from custom directories without using the HIERO_PLUGIN_PATH environment variable.

Workaround
Set the HIERO_PLUGIN_PATH environment variable to the path, then add the Workspaces folder with the same Folder as in the .nuke directory for the workspace .xml files

Reproduced by Support in:

Nuke 13.1v2 - Windows 10, macOS 10.15

Nuke 13.1v1 - Windows 10

Nuke 13.0v1 - Windows 10

Nuke 12.0v1 - Windows 10, macOS 10.15

Nuke 11.0v1 - Windows 10

Nuke 10.0v1 - Windows 10

Nuke 9.0v1 - Windows 10

Earliest version tested
Nuke 9.0v1 - This issue appears to be in all versions of the product