Based on the OP they were complaining about the 10 second process time for Scrivener to do what it is documented as doing. Hence they are going to take the hit and live with it.
Scrivener uses the Mac OS built-in compression tool. So it wouldnât be difficult if Appleâs tool kit supports it.
A better short term solution for you would be to make unzipped backups.
Yes, agreed. I was responding to your reply that mentioned â10 minutesâ, which would be an entirely different level of friction and worth much discussion to find a workaround. 10 seconds, not so much.
Best,
Jim

Scrivener uses the Mac OS built-in compression tool. So it wouldnât be difficult if Appleâs tool kit supports it.
Iâm curious (on a technical level) if thatâs âjustâ using the included command line ZIP tool or if that code is somewhere âbaked inâ. Because the command line tool definitely offers a parameter -0
(Zero) = âstore onlyâ.
FWIW, I open projects as I need them, but then generally leave them open indefinitely. Every so often, Iâll either close Scrivener altogether, or step away from my computer for long enough that auto-close does it for me. So backups rarely disrupt what Iâm doing.
OTOH, I open a lot of support-related projects, which are more or less disposable. So my usage probably isnât typical.
Itâs not using the command line interface â that is, it doesnât launch a Terminal window â but beyond that youâd have to ask Keith.