Weakness in recognising file deletion on server - no interest/

Hello NC users & gurus,
I opened a github item

because of a weakness in sync algorithm that is bugging me (forcing some tedious workaround). I see that nobody has looked at the defect. Is it possible that nobody else encounters the same difficulty, that is having files removed centrally by retention app, and being unable to effectively enforce that removal?
Maybe I made something wrong in the design of the system. In my case, lots of files are created on the periphery, but they need to be submitted to a central retention process.
Any suggestion is welcome to workaround that limitation. It would also be nice if some other user would agree this is a program weakness.
Thanks! hj