ID 556657 - MXF files are Read in Full Range regardless of the Data Range knob

Problem summary:
MXF files are Read in Full Range regardless of the Data Range knob.
 
This issue appears to affect all of Nuke's MXF Codec Profiles (4:4:4, HQX, HQ, SQ, LB), Patterns (OP-1a, OP-Atom), and whether or not the MXF footage was originally encoded in Full or Video Range.
 
Customer reported version:
Nuke 15.0v1
 
Customer reported platform:
macOS 13 Ventura
 
Steps to reproduce:
1) Launch Nuke, create a Read node, and select some MXF footage.
2) In the Read node's Properties, switch the Data Range knob from Full Range to Video Range.
3) Observe how the resulting image does not change, unlike the behavior in Nuke 14.0:

 
Expected behavior:
The user should be able set whether MXF files are Read as Full Range or Video Range.
 
Actual behavior:
Nuke always reads MXF files in Full Range and this cannot be changed with the Data Range knob.
 
Workaround:
No known workaround at this time.
 
Reproduced by Support in:
Nuke 15.0v1 - Windows 10, macOS 13 Ventura
Nuke 14.1v1 - Windows 10, CentOS 7 - Regression

Unable to reproduce bug in:
Nuke 14.0v6 - Windows 10, CentOS 7
 
Earliest version tested:
Nuke 14.0v6 - This issue doesn't appear in this version and has regressed