The time zone adjustment would be +0?

Sorry, I've not dealt with time zone stuff, so I admit ignorance.

Okay, I'm still not sure what the problem is?

Downtime Times - Uses Eve window time in Neocom only? (This would mean that starting the bot during DT would cause it to be unable to log in and have a wait timer because it doesn't know what the Eve time is.)

Local Timers - Uses VM/PC time to decide when to start/stop/idle the bot (Uses guest OS time on a VM, right?)

If someone is using a proxy or VPN, they may want to set a different time on their VM/PC so that it matches with the fake IP location's time? So what if someone was in a +/- time zone and set their VM/PC to UTC instead of their own? This would mean that there would be 3 time zones in play; Local, VM-UTC-Fake, Eve-UTC. Regardless, their VM/PC time is different and it is their responsibility to set the timers up correctly.

I'm pretty sure that EP does DownTimeCheck within StartEveAndLogin, right? I'm guessing it gets the time for use later, so you can calculate the DT start and stop? So... DownTimeCheck probably gets the the current EveTime and uses EPStartTime to calculate when DT is based on how long the bot has been running?
What about having DownTimeCheck also use the local VM/PC time? Once it logs into Eve for the first time, it already gets EveTime with DownTimeCheck. Could DownTimeCheck also get the VM/PC time, then you could use the VM/PC time or EveTime to check if Downtime passed?

In AHK you could use A_NowUTC to get the UTC time, which would be my first thought.

Scenario:
EveDownTimeStart = 10:00, EveDownTimeEnd = 10:30 (set in EP UI)
EveTime = 10:00, LocalUTC = 10:00 -========- EveTime - LocalTime = 0 as LocalTimeDif
EveTime = 10:00, LocalUTC = 04:00 -========- EveTime - LocalTime = 6 as LocalTimeDif
EveTime = 10:00, LocalUTC = 22:00 -========- EveTime - LocalTime = -12 as LocalTimeDif

DownTimeCheck addition: If EveTime is not open/found (because Eve is Closed), get LocalUTC for VM/PC.
If( LocalUTC + LocalTimeDif >= EveDownTimeStart && LocalTime + LocalTimeDif <= EveDownTimeEnd) ; 4 + (6) = 10 ; 22 + (-12) = 10
DownTimePassed = True

I dont bother with local time in VM. Just set local time to be UTC.

>I'm pretty sure that EP does DownTimeCheck within StartEveAndLogin, right?
Yes
>Once it logs into Eve for the first time, it already gets EveTime with DownTimeCheck.
Bot does not scan time from the game.

End timer within DT time and you will have no problems with status of belts. Every time bot jumps to new system it will reset status of belts in new system. Just enable traveling (if you dont want to travel, add the same system twice) and bot will mine nonstop