For when Multiple ASP.NET Core Applications In Process per Application Pool ?

I'm following .NET Core and ASP.NET Core since day one.

I have a huge .NET backend (ASP.NET Web Api) that I would like to port to .NET Core.
Since version .NET 2.2 that my application is 100% compatible with both .NET Framework and .NET Core.

My first trials with .NET Core + ASP.NET Core + Kestrel + IIS was exactly 4.4 slower than .NET Framework + ASP.NET + IIS.
The fun boys always tried to kidnap my arguments until In-Process model appears with the argument that is 4.4 faster (funny). Indeed it's not 4.4 faster, it's now exatly the same speed as .NET Framework + IIS in a real live world, so this long story suits to mention that the old model Out-Process it's not even an option.

My issue and it's currently the only think that stops me now to port to .NET Core is the absence of "Multiple ASP.NET Core Applications In Process per Application Pool" as we have with .NET Framework + IIS.
.NET Core it's very near with .NET Framework that it's not there iet (for me) because of this.

I wished that this application indeed does not requires this option but it's not the case, so my question as the title mention is:
For when Multiple ASP.NET Core Applications In Process per Application Pool ?

Thank you,
Hugo.