Empty projects runs max 60 fps on 2019.2.13f1

The Other Category was previously not shown unless a sample was selected. That bug is fixed now. Profiling playmode in the Editor always includes time for the Editor being rendered around it. There are other system that attribute to Other but EditorLoop is likely by far the largest one while propfiling playmode. (Other categories are anything in timeline view that has a color that doesn't map to the CPU Usage chart)

Ergo: nothing changed, it just became way more visible. Nothing needed for you to do here, except what held true before this: measure the performance in a built player, not in playmode, if you need accurate numbers to find issues. Use Playmode profiling to iterate on issues found this way.

You can toggle the box for "Other" in the legend of the chart. That way you can hide the Other category again. Notice however, as shown in your screenshot: The EditorLoop still takes a significant amount of time on the main thread. This also changes the timings of scheduled jobs and render commands. That means while in the Editor, your game might have all the time it needs to render while the Editor does calculations, a built player might be done on the main thread faster and then need to wait on the Render thread the next frame. In the Editor, we can "hide" some time through toggles, but this kind of base difference is just not going to go away soon.

 

For reference: this is the bug that was fixed.

 

The Editor doesn't actually VSync (as in, sync to VBlank on GPU). It simulates VSync and emits that WaitForTargetFps sample. See the documentation of common Rendering and VSync samples for more details.