The good news is it seems dev has finally released new modules that are more configurable, but I have not looked at how much complexity was shifted to propertysources and how maintainable that will end up being. They tied to ssh.user/ssh.pass still, though, so you will still run the risk of incurring costs unexpectedly if you use those for non-LMConfig reasons (like errdisabled port detection). I think it is possible to disable LMConfig modules in the subtree alert tuning, though, so that may mitigate the risk.
OSS tools do a much better job than LM did previously, hoping this brings some parity (and fixes for non-change thrashing we see all the time). I would never dream of editing a 1200+ line module and then have to merge changes into updates later.