[Bug] Text selection highlight and Transform bounding box become invisible (Still clickable)

[System Specs]

• CPU: AMD Ryzen 9 9950X3D

• GPU: NVIDIA RTX 5070 Ti (Latest Studio Driver)

• RAM: 64GB

• OS: Windows 11

• Display Setup (3 Monitors Total): Main Monitor + Secondary Monitor (24-inch) + Tertiary Tablet Monitor (Xiaoxin Pad 12.7 via SuperDisplay app).

[Symptoms] While editing in Premiere Pro, the UI overlays in the Program Monitor randomly disappear.

1. When selecting text, the blue highlight background does not show up.

2. When an object/text is selected, the transform bounding box (scale/rotation handles) is completely invisible.

3. The elements are still active and clickable. I can still blindly click the corners to scale or type to edit text, but I just can't see the UI guides.

4. Important context: The Program Monitor is ALWAYS on the Main Monitor (directly connected to the GPU). The other two secondary monitors (including the SuperDisplay tablet) are only used for panels like Effect Controls or Timeline.

5. Restarting Premiere Pro temporarily fixes the issue, but it keeps happening after a while.

[Troubleshooting Steps Already Taken (None worked)] To save time, here is the list of things I have already tried without success:

• Checked that "Show Transform Controls" (wrench icon) is enabled.

• Reset workspace layout (Alt+Shift+0) and switched panels.

• Tweaked UI brightness in Preferences > Appearance to force redraw.

• Cleared Media Cache.

• Clean installed NVIDIA Studio Driver.

• Disconnected SuperDisplay and toggled its hardware encoding settings.

• Disabled "Hardware-Accelerated GPU Scheduling" (HAGS) in Windows Settings and rebooted.

• Toggled Renderer from CUDA to Software Only and back to CUDA.

• Turned off "Background Application Max Frame Rate" in NVIDIA Control Panel.

It feels like a UI rendering/overlay conflict triggered by having a mixed multi-monitor setup (physical + virtual display driver), even though the Program Monitor never leaves the main GPU display. Does anyone have a workaround or know if this is a known bug with the latest Premiere / RTX 50-series?