How to reproduce:
1. Open the “ReproProjectGPUBound.zip“ project
2. Open the “SampleScene“
3. Enable Development Build and Autoconnect Profiler in the Android Build Profile
4. Build and Run for Android
5. Attach the app to the Profiler
6. Rotate the device to the Landscape orientation
7. Observe the Highlights and CPU Usage modules in the Profiler

Expected result: The Vsync is bounding the frame time
Actual result: The GPU field in the Highlight module shows that the GPU is exceeding the target frame time and in the CPU usage module you can see the frame time is bound by Vsync

Reproducible with: 6000.0.45f1, 6000.1.0b13, 6000.1.0a8
Could not test with: 2021.3.50f1, 2022.1.0b1 (4897ee769494), 2022.3.60f1 (Highlights module is not present in the Profiler)

Reproducible environment: macOS 15.3.1  (M4 Max), Windows 11 (Reporters)
Not reproducible environment: No other environment tested

Reproducible with these devices:
VLNQA00612, Samsung Galaxy S24 (SM-S921B), Android 14, CPU: Exynos 2400, GPU: Ltd.

Not reproducible with these devices:
VLNQA00468, Huawei - (ELS-NX9), Android 10, CPU: HiSilicon Kirin 990 5G, GPU: Mali-G76
VLNQA00518, Google Pixel 4 (Pixel 4), Android 13, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00335, Samsung Galaxy S20+ 5G (SM-G986B), Android 10, CPU: Exynos 990, GPU: Mali-G77
VLNQA00626, iPhone 16 (MYE73QN/A), CPU: Apple A18 Pro, GPU: Apple designed, OS: 18.3.1
VLNQA00232, iPhone 8 Plus (MQ8M2ET/A), CPU: Apple A11 Bionic, GPU: Apple designed, OS: 16.7.10

Notes:
- Reproduce with both Vulkan and OpenGLES3 Graphic APIs, but with Vulkan it is a rare occurrence, OpenGLES3 gives a consistent reproduction
- Might need to rotate the device to Portrait and back to Landscape orientation several times for the issue to reproduce (according to the reporter within 10 rotations the issue should reproduce)
- Does not reproduce in the Editor with the Simulator
- Happens with Frame Timing Stats enabled and disabled