Mixed mode debugging performance

[MarchingCube]

Disclaimer: I'm not sure if this issue belongs here but I have no better idea at the moment.

I have a project that has managed (.NET 5) components and a bunch of native (C++) components as well.
I have a common entry point that starts our runtime host (in C++) and then runs .NET code as well.
The problem that I've noticed is that with mixed mode debugging enabled ("nativeDebugging: true" set in a launch profile) time to start my application triples (from 3 seconds to 10 seconds) when the debugger is attached. Using only native or managed debugger also gives fast results. I've disabled symbol loading as well since this is an easy time gain but still something is happening that really slows down startup.

It is fairly hard to find good information about this anywhere so I'm wondering if this is expected or if there is anything that app developers can do to reduce this overhead? From my limited profiling of app startup it looked like as if app spends way more time in JIT when compared to starting without a debugger. This overhead also was fairly consistent but I'm not sure what is the best way of profiling app startup with a debugger attached to actually pinpoint slow path.