ID 232652 - Path Substitution doesn't work for the project font path

Problem summary
Path Substitution and filenameFix() are not applied to the project font path.

Customer reported version
nuke.9.0v7

Customer reported platform
windows10

Steps to reproduce

1) Open Nuke on Windows

2) Open Project Settings, and set the free_type_font_path knob to a network path with a custom  .otf font in 

3) Uncheck include system fonts, then Rescan font paths

4) Create a Text2 node, and set the font to the custom font

5) Save the Nuke script to the network

6) Open Nuke on Mac or Linux

7) Open Nuke Preferences...

8) Create a Path Substitution, like the one shown below:

9) Reopen Nuke on that system, and open the saves Nuke script from Windows

10) You will get an error saying Font is not available

Workaround
Manually change the free_type_font_path knob, or automate it with a Python script.

Or use a Text rather than Text2 node, as it works correctly.

Reproduced by Support in
Nuke 12.1v4 - Windows 10, macOS 10.13.6, CentOS 6.8
Nuke 12.1v1 - Windows 10
Nuke 12.0v1 - Windows 10
Nuke 11.0v1 - Windows 10
Nuke 10.0v4 - Windows 10
Nuke 10.0v1 Windows 10
Nuke 9.0v9 Windows 10
Nuke 9.0v1 Windows 10
Nuke 8.0v6 Windows 10, macOS 10.13.6, CentOS 6.8
 

Expected behavior
For the fonts to be substituted on the different OSs

Actual behavior
Path Substitution was not applied