Reproduction steps:
1. Open the attached “IN-98078.zip” project
2. Open the “Playground” Scene
3. Enter Play mode
4. Click and move around with the mouse cursor in the Game view
5. Observe the Console

Expected result: Console shows ordered sequence: "Frame N: Input Axis Values Changed" followed by "Frame N: MutateCameraState" with consistent movement detection
Actual result: Console shows "MutateCameraState - Moving: False - Path: Fixed Update" alternating with "MutateCameraState - Moving: True - Path: Late Update" in the same frame numbers

Reproducible with: 3.0.1, 3.1.3 (2022.3.61f1, 6000.0.47f1, 6000.1.0f1, 6000.2.0a9)

Reproducible on: Windows 11
Not reproducible on: No other environment tested

Notes:
- Also reported on Unity Discussions [https://discussions.unity.com/t/different-frame-loop-behavior-if-vcam-is-viewed-in-inspector|https://discussions.unity.com/t/different-frame-loop-behavior-if-vcam-is-viewed-in-inspector]
- When the “vcam” GameObject is selected in the Inspector, the update pattern is more consistent, showing a regular sequence of Late Update (Moving: True) followed by Fixed Update (Moving: False) calls, though the core issue of mismatched movement detection between Fixed and Late updates remains