This is more question than answer, but nobody else is following up, so here goes.
Local is separate interface on your laptop, just like your ethernet adapter and wifi adapter. Just because a program listens on 127.0.0.1:1080 (localhost socks proxy) does not mean that it will listen on another interface. "access the laptop's localhost from my device" is not possible. Proxies, that are not intended for public use, normally listen only on localhost for security reasons.
If you MUST connect to the laptop's localhost socks port, you need "tcp tunnel" software running on your laptop to listen on a reachable interface and redirect it to the local interface. Realize that you are creating a security risk if you do, because the Tor client on your laptop won't be able to tell whether it's you connecting to the local socks proxy port. It's been a decade since I last looked for "tcp tunnel" or "tcp proxy" software, so I don't know which to suggest -- you'll have to research it.
And the questions... When you say "virtual router", do you mean http://virtualrouter.codeplex.com/? Something else? Is it bridging, or routing? The page is unclear. It would become clearer if you attached the results of running "ipconfig /all" on the laptop while the virtual router was up. Please also indicate your device's IP wile connected -- Fing will get that easily if you need it.
What do you mean "Orbot is unable to connect via the wifi's proxy"? When you connect to your virtual router, can you connect to the Internet? Apart from Tor, is there a proxy involved?
It would be ideal for you to do this with Orbot because on a rooted phone it can route all your traffic through Tor. Going through your laptop's Tor client means configuring your browser or whatever software to use a socks proxy, in which case you are trusting the browser or whatever not to leak.