Botting on 1 account about 8h a day in past 2 weeks, all fine.
Anyway... Virtual Machine, v-p-n or prxy, changing processes, using bnet app or not... IT DOES NOT MATTER.
Most of the warden is embedded in battle.net.dll file. It scans the Diablo III.exe and other processes that are attached/injected into it. So there is no a single "safeguard" like few above that will prevent the warden seeing your bot except doing a 'double game whammy' where you make second instance of the game on top of the original. That is the protection that works 99.9%.
Like many people suggest, it is good practice not to let it do 100 games/h and similar precautions but that will only help you because if warden locks onto DB process or someone in blizzard notices weird account behavior, you are likely gonna get smoked.