Worth mentioning that the author speculates that this happens not for a nefarious reason, but in a binary tree search to locate your zoom cookie.
It was really odd they didn't bother.
https://jvns.ca/blog/2014/09/27/how-does-sqlite-work-part-1-...
You could do similar at API entry points.
Or, if you're after writes, it would be simpler to attach an "on insert/update" trigger that just records the changes in another table. See https://www.sqlite.org/undoredo.html for an example of using triggers this way.