With the speckle-sharp v2 SDK, it will search for converter “kits” (.NET dlls) in %appdata%\Speckle\Kits folder.
It seems this behaviour is causing this other plugin an issue because its scanning all loaded assemblies for that AssemblyCompanyAttribute
While the v2 code is setup to load kits, For the Unity connector, this is not required functionality, since all the required converter dlls are already directly loaded by the Speckle Unity Packages.
I would suggest you try overiding the path the SDK looks for these kits.
If you call this SpecklePathProvider.OverrideKitsFolderName function before trying to use anything speckle related (e.g. put in an Awake callback)
I’d suggest setting this path to some empty folder in your project, or in temp folder, since we don’t actually want it to find any dll files, but we do want to give it a valid path to try.