[NiLuJe]

Modifying the rcS to handle a reinstall post-update doesn't make sense, because the rcS will be replaced by the update.

You can, instead, do that via the usual loop0 udev trick, as that'll survive and is far less intrusive.

Note that, as far as KFMon is concerned, you should still trigger a reboot after install and not launch KFMon manually, because how KFMon is launched is critical to not subtly breaking things in fun and interesting ways.

As far as the KFMon release schedule: there isn't one ^^. It's basically "when necessary". The OCP packages actually use a rolling build of the current master.