SQLite cannot accept random contributions. It's on A350 flight systems, where failure is not an option. The maintainers are able to uphold this quality, but random contributors are not.
It appears that the true desire is log shipping (archived logs, transaction logs, etc.) - the ability to move transaction data between databases, perhaps in multimaster.
The only way such functionality is getting into SQLite is if the project agrees to write it, likely for major funding.
A fork implementing these features will be regarded with interest, but will not be accepted without substantial rework.