Okay im not certain but i think someone found a solution to the reverting crontab configs. Reboot just after editing and before the revert is done (you mention a couple of hours).
Here they mention the crons inside ‘/usr/local/config/config.xml’ I wasn’t aware of them sorry. 
I’ll try doing the earlier mentioned crons to see if the edits persist if i reboot right after.
Edit: Not working with the before mentioned crons. trying the xml now.
Edit2: Found the solution i think → How to Make Persistent System Changes (crontab, etc)
Although ‘wdnas_backup’ doesn’t seem to have any of any of the settings we are interested in and wdnas_config is not remembered after reboot. Maybe someone smarter than me can figure this one out?
wd_crontab.sh (/usr/local/modules/script/wd_crontab.sh) looks like this:
Edit3: Well i deleted all the sh files mentioned earlier & stopped all i could. Then i #'ed out the two previous crons completely and made them both as locked down as possible with chmod 000. Then we’ll see if they revert. In the config.xml i just removed ‘pull_wdlog_config’ lines.
I haven’t been able to find & read ‘random_check’ & ‘expire.sh’ yet so i’ll leave those for now. Also no chmod for config.xml because it’s nice being able to configure sometimes inside of the wd html config.
