Reproduction steps:
1. Open the attached user's project "My project.zip"
2. Build and run on Quest 1, notice the HMD and controllers track smoothly with no stale frames
3. Switch the TrackedPoseDriver's UpdateType parameter (on MainCamera) to "Update"
4. Build and run on Quest 1 and notice the expected tracking lag due to frame timing issues caused by using Update
5. switch the TrackedPoseDriver's parameter back to "UpdateAndBeforeRender"
6. Build and run on Quest 1 and notice that the same frame time issues persist

Expected result: switching back from "Update" to "UpdateAndBeforeRender" does not cause frame time issues and no stale frames
Actual result: switching back from "Update" to "UpdateAndBeforeRender" causes frame time issues and stale frames

Reproduces on: 2022.1.0b1, 2022.1.0b11, 2022.2.0a6
Does not reproduce on: 2022.1.0a16, 2021.2.14f1, 2020.3.27f1
Could not test on 2019.4.36f1 due to package errors when downgrading

Reproducible with these devices:
N/A, Oculus (Quest), Android 10, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540

Not reproducible with these devices:
N/A, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650

Notes:
-This issue only seems to manifest when Vulkan, URP and URP's MSAA anti-aliasing is being used
-To see stale frames, enable them in the OVR metrics plugin in Oculus Developer Hub
-Issue is reproducible with fresh VR core templates, and making the minimal changes required (such as creating a URP asset) to configure the project