ID 586434 - Exporting baked transforms from the Tracker node is very slow when reading footage from a network

Problem summary
Exporting baked transforms from the Tracker node is very slow when reading footage from a network.
This only happens with the baked transform options: Transform (stabilize, baked) and Transform (match-move, baked).
 
Customer reported version
Nuke 15.1v2
 
Customer reported platform
Windows 10
 
Steps to reproduce
 
1) Open Nuke.
 
2) Read in some footage.
 
3) Create a Tracker node, and track some frames across your footage.
 
4) Connect the Tracker node to some footage that it being read from a network location (if it's not already) and view it.
NOTE: The issue will be easier to see with higher resolution footage.
 
5) On the Tracker node, under Export, select either Transform (stabilize, baked) or Transform (match-move, baked). Press create.
 
Expected behaviour
The Transform node should be created very quickly (almost instantly).
 
Actual behaviour
The Transform node take a long time to be created, and Nuke's UI becomes unresponsive.
If you view Nuke's network usage (ie. through Task Manager) while the Transform is being exported, then you may see it increase a lot.
 
Workaround
Temporarily disconnect the Tracker node from the upstream Read node, before exporting the baked Transform.
 
Reproduced by support
This bug has been reproduced in:
Nuke 15.1v3 - Windows 10 - macOS 12
Nuke 14.0v4 - Windows 10 - macOS 12 - REGRESSION
 
Unable to reproduce bug in:
Nuke 14.0v3 - Windows 10 - macOS 12
 
Earliest version tested
Nuke 14.0v3 
- This issue doesn't appear in this version and has regressed