agreed. In the mean time we added a new ProfilerRecorder API in 2020.2 because we build ourselves into a corner a bit on the native side for the Recorder API and wanted to instead offer one such API to record both the samples created by ProfilerMarker APIs as well as Profiler Counters, such as the stats shown in the different Profiler Modules. This new API does not yet include the capabilities to record GPU but we’ll get there too.
We’re going to go over the different modules and convert them all to the new native Counters API (instead of the old “stats” way to record these values) and evaluate which one of these are near enough to no cost to be left in for Release Builds while we’re at it. For 2020.2 this has already happened for the Memory, Rendering and the new Virtual Texturing Profiler Module.
API to output your own Counter values is pending, an editor to slot any Counters together in a custom module is already added. Stay tuned for more details and documentation (including what counters there are and which ones are in Release) as we tie that all up during the alpha/beta cycle, but feel free to already give that a try 