Worth mentioning that the uninstaller sets the cookie by adapting your cookies file after reading contents of the file entirely unrelated to Zoom.
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.
In the same way I'm reading your mail if I look at it to see whether it's my mail, and then put it back down when I see your name.
That is to say, not at all.
It's like Zoom goes through your temp password database to change your saved password for zoom.
Then again, planting a 10 year cookie that can only exist when edited outside the browser's sandbox is a helluva effective long term marker for a particular person. Maybe they just want to keep tabs on you. :)