OK, but that is an issue of how much information is stored in the time tuple.  There is no UTC offset or timezone information stored in the tuple beyond whether DST is on or not.  That is just an inherit shortcoming of the time tuple.  You can't fix that without adding a new field to the time tuple itself.

I am personally not about to do that, but if someone wants to write a patch it might be considered.  But you will also need to discuss why this should be done over just moving to datetime (and possibly fixing it there if there are problems there as well).