ID 599141 - The Roto/RotoPaint node's "black outside" knob produces inconsistent results

Problem summary:
The Roto/RotoPaint node's "black outside" knob produces inconsistent results 
 
Shapes and strokes are affected differently depending on the state of other knobs, like "round to pixels"
 
Customer reported version:
Nuke N/A
 
Customer reported platform:
Windows 11
 
Steps to reproduce:
1) Launch Nuke and create a CheckerBoard node in the Node Graph
2) Create a RotoPaint node
3) Add a Bezier shape to the RotoPaint, such as a Rectangle
4) In the Properties panel, set the Rectangle's source to "foreground":

5) Switch to the Clone tab, and disable the "round to pixel" knob
6) Set the translate x/y to decimal values, and observe the resulting image 
7) Disable the "black outside" knob
8) Adjust the translate x/y values again, noting that the translation now appears to be rounded to the nearest pixel:

 
Expected behavior:
The Roto/RotoPaint's "black outside" knob should not offset the source image or make it rounded to the nearest pixel.
 
Actual behavior:
Disabling the "black outside" knob for a given layer inside a Roto/RotoPaint node can cause the resulting image to be rounded to the nearest pixel, even if "round to pixel" has been disabled and impulse filtering is not selected.

This also affects other RotoPaint tools, such as the Clone brush, but the results are slightly different. In the GIF below for example, the blue lines are being adjusted by a Clone stroke and the green lines are being adjusted by a Bezier shape. See the attached roto_clone_testing.nk file for the complete setup used to create these scenarios.
 
The top row of images demonstrate how disabling the "black outside" knob only seems to incorrectly affect Bezier shapes when "round to pixels" is enabled, while the bottom row of images show that both Bezier shapes and Clone strokes are affected to different degrees when "round to pixels" has been disabled:

 
Workaround:
No known workaround at this time.
 
Reproduced by Support in:
Nuke 16.0v1 - Windows 11, macOS 14 Sonoma
Nuke 15.0v1 - Windows 11
Nuke 14.0v1 - Windows 11
Nuke 13.0v1 - Windows 11
Nuke 12.0v1 - Windows 11
 
Earliest version tested:
Nuke 12.0v1 - This issue appears to be in all tested versions of the product