If you want you can add it and I will test if it works in the next beta version.
I tried it several times and also have a file from year 2018 and it was stored correctly and when creating the archive (.zip) Accessed timestamp was not updated.
This website says.
For Windows XP, it is turned on by default.
For Vista, Windows 7, and Windows 8, the attribute is disabled by default.
Windows 10 and Windows 11 should behave the same way as in Windows XP.
I thought it was a bug and didn't know that Tar was developed almost exclusively for Linux/Unix.
Initially I thought that all archive formats provided by Directory Opus behaved exactly like the installed operating system, that is, it supports NTFS (Created, Modified and Accessed) timestamps.
But Tar doesn't support that and it looks like it only supports Modified timestamp. It would be good if it can be added to your documentation.
I will probably only use
.zip, .rar and .7z
in the future because they support Created, Modified and Accessed timestamps.