[ed_davidson01]

Figured out the problem, but no solution. It appears that every time a Job gets made from the Record and Play dialog, that job is actually set to record four hours ahead of the exact time I confirmed the Record and Play command.  I don't know how to solve this, I tried adjusting timeshift settings to no avail. Can't figure it out for the life of me. This is all on 18.2, by the way.

That's weird.
I wonder if there is something wrong with the locale time conversion.
Does the four hours change if you set Record and Play time to something other than 4 hours?
Can you tell if your system clock time is the same as the Kodi clock time?
Can you see if it does the same thing in Windows?
Are you using any vpns from a different time zone? 

It's always four hours. My timezone is four hours behind GMT. Kodi's clock and the system clock are synched. All of my Kodi connections, outgoing and ingoing, are using my public IP, and I cannot check Windows functionality.

It works if I set my clock to GMT and set it back after the job is created. The job will shift back four hours and be correct, but next time I set a job in EST it'll still use GMT time for scheduling. I'm running out of options, here.

Here's hoping we can get down to the solution here. Thanks for sticking around thus far.

How about shifting the time in simple client