I had some small hope that this would be fixed in Revit 2026.1 patch, didn't happen.
If you want to complain here is the main thread in the Revit Preview feedback.
So I guess the easiest option to 'isolate' the plugin would be to ILRepack all the dependencies inside the main plugin dll.
I create a package to help ILRepack all the dependencies in a single dll. I kinda need to create a video about that.
Here is the package:
If you add this in your csproj, all the references will be repack inside the main dll. (Build time increases depending on how many dependencies your project has.)
<ItemGroup>
<PackageReference Include="ricaun.ILRepack" Version="*">
<PrivateAssets>all</PrivateAssets>
<IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets>
</PackageReference>
</ItemGroup>
<PropertyGroup>
<ILRepackCommandExtra>/allowdup /allowduplicateresources</ILRepackCommandExtra>
</PropertyGroup>
The other option would be implement the AssemblyLoadContext yourself, but that add code complexity and only works with .NET Core (Revit 2025+).