as a matter of interest do you know which database this is, where it is located, and whether you could use this in either migration to a newer version of Kodi and/or on a fresh install of the same version of Kodi to keep your "Kodi" watched status ??
I'm
certainly no expert but as far as I'm aware the watched status/resume points are simply located & ammended as required on the main video database table itself, i.e. your
MyVideosxxx.db. (Rather than there being separate files recording that particular info externally that you could backup separately etc.).
The Kodi backup add-on is obviously one possibility if you're wiping & reinstalling the same version of Kodi as that backs up the entire MyVideosxxx.db & you'd be retaining the same actual DB version anyway so fairly straightforward in that instance.
It's when you're shifting versions things can potentially require more effort or get a little more tricky & we all have different ways of maintaining our libraries. From those that use local .NFO files only & don't externally scrape any media information right the way through to those that use a MySQL server running on a NAS or another dedicated device to maintain their Kodi library.
I'm continuing to use a MySQL server for my Kodi library on a NAS so this exact procedure is incredibly simple for me as Kodi automatically migrates the entire library to new database tables if Kodi is upgraded & it detects older .DB versions. (The older DB tables are also retained & preserved so if I suddenly changed my mind after said upgrade if there was something I didn't like, I could immediately revert back & my original library would still be exactly as it was. If happy with everything after upgrading, I can simply bin the older DB as or when required). Obviously, that's another option & it's a damn useful one if you use more than one device with Kodi installed, or one device that you're frequently flashing the firmware wiping Kodi each time in turn.
That simple migration includes all of my watched status, resume points, my own * user ratings, & the play counts/dates when I last watched any given movie/TV show. Otherwise, because each Kodi device essentially connects as a client, they all share the same central library DB as it's configured & each can update or modify the library seamlessly.
Having said that, I think there are some differences for those that use local .NFO files only for managing their Kodi library rather than externally scraping media information from a remote source but I'd assume anyone already setup to use .NFO files to manage & maintain their Kodi DB would also be aware of the required entries in their advancedsettings.xml file too & the correct export/import procedures respectively.
Kodi's own built in export/import database options could also be used but I never used them myself so I can't really give any specifics there. Given that we often test multiple MINIX devices especially with Kodi and/or how frequently we flash new firmware versions as well, by the time I actually needed my first library migration I'd already decided it was going to be far, far simpler just using a single library on the MySQL server instead.
Kodi also may not import watched status or resume points by default in certain circumstances so you simply need to add a couple of lines to an advanced settings.xml file to ensure the info is correctly imported.
More info on those particulars here including the specific tags that need to be added to the advanced settings....
https://kodi.wiki/view/Import-export_library/Video .
Granted, most users tend to run a single device with a single library, so either the backup add-on or the export/import options would probably be preferable & just use Google to fill in any blanks depending on a fresh install or an upgrade
.