VSSDK: COM server with .NET 7.0+ fails to locate runtime when hosted in VSIX editor

Description:
We are developing a VSIX extension that provides a custom editor to process .NET assemblies. Since VSIX itself runs on .NET Framework, we had to separate the editor into its own assembly (.NET 7.0 or later) and connect it with the extension via COM. The editor is implemented using VSSDK, because VisualStudio.Extensibility does not yet expose the necessary APIs.

Problem:
The setup works correctly when the COM server targets net6.0:

• The COM host first searches 'C:\Program Files\Microsoft Visual Studio\2022\Professional\MSBuild\Current\Bin', and then 'C:\Program Files\dotnet'.
• The framework is found, and the server starts as expected.

When switching the COM server to net7.0 (or higher):

• Starting with .NET 7.0, multilevel lookup is disabled, so only the directory 'C:\Program Files\Microsoft Visual Studio\2022\Professional\MSBuild\Current\Bin' is searched but the 'C:\Program Files\dotnet' directory is not searched at all.
• The log outputs: 'No frameworks were found'.
• The whole extension crashes.

Question: Is there any supported way to override or configure the search path for the runtime frameworks, so that instead of only scanning 'C:\Program Files\Microsoft Visual Studio\2022\Professional\MSBuild\Current\Bin' it will also include (or redirect to) 'C:\Program Files\dotnet'.

What I've tried:

• Update VS to the latest version
• Setting 'DOTNET_ROOT' env variable to "..\ProgramFiles\dotnet"

I've attached logs when using both net6.0 and net7.0:
COM host log - net7.txt
COM host log - net6.txt

Start by comparing the attached COM host logs for net6.0 and net7.0, focusing on the runtime framework search paths and the “No frameworks were found” result. Research the VSSDK COM-host runtime configuration and determine whether a supported path override exists; done means documenting or confirming a supported way to locate the .NET runtime.