I would try to reverse engineer the history table to understand what, if any, rules are available to customize. You may be able to apply a datetime control or other formatting options, depending on what you find.
We had a similar issue, where I applied the pxDateTime control to the parameter of a field value. While the format displays in the proper locale's structure (dd/MM/yyyy hh:mm:ss) instead of the ugly Java GMT timestamp, it is not converting to the right TIME ZONE first.
So using example timestamp: '20180125T010100.000 GMT' passed in as a parameter to a field value, would display as '25/01/2018 01:01:00 AM", which is an acceptable structure, but I expect it to display in Eastern Standard Time, which actually changes the calendar date since it is 5 hours behind, so it should actually show 24/01/2018 08:01:00 PM".
What is strange is that the exact same control, used in any other UI section, displays my expected format in the proper time zone. Just not in the parameters of field values.