For purely development needs I recommend one of the approaches outlined in this question/issue so that you don’t need a VM at all; you can run hcidump remotely from your RPi Zero W (simultaneously with your “in-use” collector running there). An alternative, easier but less realistic option is to capture a short hcidump recording on the RPi into a text file and “playback” it on your development machine (also described in the question/issue).
If you go with the hcidump-over-ssh approach, do note that you don’t need to use the scan command on your “development instance”, as your “production instance” of the collector is already running it on the RPi (as long as the collector is running there of course). Basically: hcitool (the scan command) must be running exactly once on a device (trying to run multiple times simultaneously likely results in errors), while hcidump (the dump command) can be running any number of times on the same device; they will all receive identical feed of data as long as the scan is active.
If you specifically want to use a VM for development (don’t want to or can’t install development tools on your host), the above approaches can be used there too, or you can use a method called “USB Passthrough” which is supported by most VM hypervisors (you didn’t specify which one you are using, Hyper-V, VirtualBox, etc…) which will basically pass through the entire USB device to the VM, and then the VM will see it as a regular USB device as if it was attached to a physical machine. This way the host OS doesn’t even need to understand what the device is. Do note that the Bluetooth dongle you’re using must support Bluetooth Low Energy, some cheaper dongles only support Bluetooth Classic and thus can’t listen to RuuviTag broadcasts.
Out of curiosity, what extended values are you going to add?