For such profiling to be effectively usable, you have to disable all plugins and scroll for a long time (20-40 seconds). For profiling to be valid, the thing you want to measure must be isolated as much as can be done.
Otherwise, the CPU time that goes into startup (loading plugins, config, lexers) skews the measuring beyond any good use. Imagine what happens if the code parser runs over your source while you scroll. What will appear in the profile?