already dismissed as a won't fix by @mbabker here #22629 and work done here #22751

It was a purposeful design decision to allow the CSV files to be parsed consistently by machine tools and not need to worry about things like timezone offset. Otherwise, the timestamps must include timezone offset to be usable.

Also note that any changes to the existing data format can only be made in major versions as changes to the data format could be considered a B/C break (treat the resulting CSV as you would a REST API endpoint basically), so if a change is going to be entertained it needs to go into 4.0 and it needs to be decided pretty quickly as technically the beta phase should not be introducing new breaks.

Thanks for the reply!

This should be closed as intended behaviour