ID 569723 - Nuke renders 30 FPS MXF files at 29.97 FPS

Problem summary:
Nuke renders 30 FPS MXF files at 29.97 FPS
 
Customer reported version:
Nuke 15.0v4
 
Customer reported platform:
Windows 10
 
Steps to reproduce:
1) Launch Nuke and create a CheckerBoard node in the Node Graph.
2) Create a Write node and render a 30 FPS MXF file, like so: 

3) Create a Read node and load the rendered MXF file.
4) In the Read node's Properties, switch to the Metadata tab and search for "rate", observing how input/frame_rate and mxf/track0/edit_rate are equal to 29.97 instead of 30:

 
Expected behavior:
Nuke should create MXF files at the FPS specified by the mxf_edit_rate_knob.
 
Actual behavior:
30 FPS MXF files are rendered at 29.97 FPS, but any other values for the mxf_edit_rate_knob (23.98, 24, 25, 29.97, 50, 59.94, 60) appear to work as expected and create MXF files with the specified FPS.
 
Workaround:
No known workaround at this time
 
Reproduced by Support in:
Nuke 15.0v4 - Windows 10, macOS 13 Ventura
Nuke 15.0v1 - Windows 10
Nuke 14.1v4 - Windows 10
Nuke 14.1v1 - Windows 10, macOS 13 Ventura - Regression
 
Unable to reproduce bug in:
Nuke 14.0v6 - Windows 10
 
Earliest version tested:
Nuke 14.0v6 - This issue doesn't appear in this version and has regressed