So, it looks like I can't convince you to revert things back to 2.35 behavior.

What do you suggest I do as a work around?

My TMF must have a synchronized options chain for the underlyprice/timestamp the TMF is executing. Otherwise the result is just plain wrong.

I moved the contractUpdate() call to inside the TMF and it DID load the correct options chain, but it also caused an infinite loop on the first TMF call.