This will probably work so for .NET Framework consumer projects (packages.config style), because packages are restored per solution (which closely resembles node_modules).

For SDK-style projects (PackageReference), the packages are used directly from user-level cache. This makes scoping per consumer project/solution impossible.

This is actually easily possible to do. Create a local nuget.config file setting the globalPackage directory to a local one:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <config>
    <add key="globalPackagesFolder" value="./packages" />
  </config>
</configuration>

This is then relative to the nuget.config file and nulink correctly picks it up.