I have used proxychains with 2 config files so that you can rotate proxies and still use tor. You cant use the random_chain option with 127.0.0.1:9050 because it fucks up the chain of obfuscation. One request could start with a proxy as the first hop and tor on the second. The next request would be tor then a proxy. So that would indicate the proxy with the exit node and then you would directly connect to the proxy that is tied to the exit node and that would defeat the purpose of using tor.
Now if you use 2 config options.
like proxychains -f config1.config proxychains -f config2.config midori (its an example don't use midori for this)


That way you can utilize the random_chain option while also having a chain of proxies randomly rotating with every request on top of tor. Don't expect to hack the gibson or anything but its defiantly a good delusion when making dank controversial memes. I aint hidin i'm glidin' on ssl and socks.

The only thing wrong with this method is that you can't see the output so its like its running on quit mode but i think the program is ethercap or ettercap you can visualize if its working in that program.