Reproduction steps:
1. Open the attached "IN-138432_3097806 - Profile Analyzer discrepency.zip" project
2. Open the Profiler (Window > Analysis > Profiler)
3. In the Profiler, click the icon in the top right to load binary profiling information
4. Select and open the file "outfit_designer_scale.data" located in the root of the project
5. Open the Profile Analyzer (Window > Analysis > Profile Analyzer)
6. In the Profile Analyzer, click the "Pull Data" button in the top left
7. Under the list of "Marker Details for current selected range", select "PostLateUpdate.EnlightenRuntimeUpdate" from the list (18th entry)
8. Under the "Marker Summary", observe that frame time information under "Max" entry gives a frame time of 32.47ms on frame 298
9. Click the "298" button
10. Switch to the Profiler
11. Observe the frame time of the highlighted "PostLateUpdate.EnlightenRuntimeUpdate" entry on the CPU usage

Actual result: Frame time in the Profile Analyzer (32.47ms) does not match the given value in the Profiler (0.024ms)
Expected result: Frame time in the Profile Analyzer matches the given value in the Profiler (0.024ms)

Reproducible with: 1.1.1 (2023.2.0a1), 1.3.3 (6000.6.0a2)
Could not test with: 1.1.1 (2023.1.0a3) (Crash on loading binary profiling information)

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

Note: This discrepancy is not limited to "PostLateUpdate.EnlightenRuntimeUpdate". Other affected markers include PostLateUpdate.UpdateResolution, PreLateUpdate.PhysicsLateUpdate, and Update.DirectorUpdate, among possible others.