While reading some of the (many, many) postings and bug reports on the problems and performance issues imposed by the requirement of recreating the local database in case of a full disaster recovery, I came up with this idea:
What about saving the local backup database file (.sqlite) to the backup destination?
Of course this would have to be done after the existing backup steps and after all writes to the database are committed and the file is closed. But then it could be compressed, encrypted and stored in the backup destination.
On recovery Duplicati would check for this backup of the database, thus eliminating the need to recreate it.