Are you using the same engine copy that is running or starting a new engine copy? These lines are the Profiler reporting that Resource.Get etc. took time to do, usually I see that when reusing the same engine copy (which I tend to avoid - closing the engine manually every time I want to reload). I use Windows 10 so behavior might be different on macOS / Linux / might just be so fast you don’t notice it on newer computer builds.
It does seem to be normal. One is the editor preparing everything before launching vs the engine getting what it needs on a new engine restart, there must be some mechanical differences that matter with it taking longer. Maybe it can be made more efficient / take less time in the future.
The profiler is active in debug builds and it will output things like the messages you see in the console when something in the engine takes a long time. It is not the profiler itself that is slow or causing other things to become slow. The profiler output should be considered as a help to you as a developer that there is something going on that you need to investigate (like you are doing now!)