Member stat cache results are prepared prior to saving, which causes date results to be cached in the timezone of whichever visitor triggers the cache write.
Thank you for reporting this issue, it has now been resolved. We are aiming to include any changes that have been made in a future XF release (2.2.13).
Change log:
Do not prepare member stat results prior to caching