welcome to the most messed-up topic in our industry ;)
You could do a check vs. your wanted times and programmatically updated the jobs to have the correct run times.
This could be it's own scheduled job running at some safe hour for your other times.
Or even easier when you already have gone the path to have times in code or some other setting that's stored non UTC; run the job every hour and check if it's time to do a run.
I thing this is something Episerver should make a add-on to or just fix in the core product.
I have read this article: https://support.episerver.com/hc/en-us/articles/115004106143-Scheduled-Jobs-and-Time-Changes
But I do not agree that this is good pratice by Episerver.
For customers how use scheduled jobs for buisness critical features, it is not a desired behavior. My customer is dependent on tree jobs to be run at: 10:00, 12:00 and 00:00. My epi database is an CMS 10.10.4. So execution time for theese jobs are stored in UTC time.
After the switch to daylight saving time at 25.03.2018, all jobs had their local time shifted one hour.
And since the solution is hosted on serveres in norway (witch has daylight saving time) the servers have there time changed too.
This will lead to my jobs being run at 11:00, 13:00 and 01:00. How can we prevent this?