This thread is still not about the SynoCommunity package. But regarding your comments about internal updates: Please bear in mind that in contrast to Kastelo, SynoCommunity is a community project offered by volunteers.
Yes, the different packaging approach has its downsides, witnessed by several reported issues in the past. But until someone steps up to work around that, or the publishing process for spksrc gets fully automated (with all associated infrastructure costs), having Syncthing internal updates is much better than none at all. I personally am not sure which approach to prefer, but certainly having to log into each Synology box’s DSM regularly to install package updates would be a much worse situation. The internal updater works perfectly fine as long as the package is left untouched.
Since around v1.5.1, Syncthing’s update routine is much more robust because it still has a chance to run even after finding a database schema “from the future”. So hopefully with v1.7.1 now published at least the symptoms should become mure more rare.