Ok. The RHINO_TOKEN variable is really only used for core-hour billing purposes and that only takes effect when you are running on a machine with Windows Server (ie. Virtual Machine). To run on a desktop, you will need a standard Rhino license. This can be an eval version, or just a standard Rhino license. The reason your Rhino.Compute is failing is because it can’t find a license when it’s trying to load the core Rhino libraries.
If you’re running on a Windows Server, then whenever Rhino starts up, it first checks for the environment variable and authenticates it before proceeding. My guess is that you may not have set the environment variable correctly (if Rhino itself is not starting). Follow the steps at the bottom of this guide to reset the environment variable using the correct auth token.