Regarding the second point: I finally (!) upgraded from Win7 to Win10, and the problem of timestamps that can't be modified seems to have gone away. Perhaps the code that handles it uses some Win10-specific API call? For the record, I'm still using the stable version 0.11.1.
Limitations in executing EXE files stored in encrypted folders
Strange behaviour of timestamps and attributes