How to reproduce:
1. Create a new Unity 2020.2.1f1 project
2. Open the Profiler (Window->Analysis->General)
3. Press the load button at the top-right corner of the Profiler window
4. Load in the user's attached "Unity2020.1.17f1_URP.data" (Found in the user's attached "ProfilerData.zip" file)
5. Select any part of the CPU module chart

Expected results: The timings in the data show correct timing
Actual results: The timings in the data are 0 or near 0

Reproducible with: 2020.2.0b10, 2020.2.1f1, 2021.1.0b1
Not reproducible with: 2020.1.0a1, 2020.1.17f1
Could not test with: 2018.4.30f1, 2019.4.17f1 because you can't load in data that was saved in newer Unity versions, 2020.2.0a1, 2020.2.0b9 because of the "Deserializer encountered error for 2020.1.17f1_URP.data" error

Notes:
- Trying to load data that was saved in Unity 2019.4.17f1 or earlier would either crash or not load the data with "Unable to read file data. Was this Profiler data captured in a newer Unity version?" error
- In Unity 2020.2 the chart is also empty

Workaround for cross version comparison:
Import data into Profile Analyzer and save it out as .pdata format, compare performance with Profile Analyzer.