Suggestion(s): UTCToLocal

As convenient as the utctolocal you added with the last patch is, there's a couple of bits that (imo) could be improved about it:

1) Adjust the output date format to dd MMM yyyy. As always in international communities, xx/yy/zz does not really work reliably because folks tend to interpret that in whatever way is closest to their standard. So dd/mm/yy, mm/dd/yy or whatever that may be. 3x double digits leads to confusion no matter what. Adjusting the output to dd MMM yyyy (e.g. "01 Mar 2023") eliminates that confusion and makes it crystal clear for everyone. Along the same lines, I'd suggest also changing the time from 24hrs to am/pm (e.g. 02:15pm) as the am/pm indicator then also removes any confusion there that may otherwise result in "wait..so 2am or 2pm??".
(I know, the hover explains it [at least partially, not the 12v24hrs]..but we're already seeing examples of that not being enough to avoid the confusion)

2) Allow for entry (and subsequent output) of times without a date attached. This'd open up more use cases for e.g. repeating time slots to be indicated that may not involve listing any specific date.

First two I can do with no problem (outputting month as a string and adding am/pm).

Second is trickier because I have to also show the user an indicator of 'previous day' or 'next day' when the offset is great enough. But yeah would be great for signatures etc.

Like it'd be cool to see in signatures (this trader is X hours ahead/behind you).

Do you? I mean, if the date is irrelevant and one is only talking about time, you don't need a previous/next day, you only need the correct converted time.

In cases where you do need the previous/next, the date is by definition relevant, meaning that's not a use case for "time only".