Just chipping in with a few comments. The module should save all parameters with patch, including any frozen looped state. I just checked again now and this is the case for me. If this isn’t the case for you, please file a bug on github and I will investigate and fix. 
I can’t reproduce this locally with Mac, it it keeps happening please open a ticket with exact steps.
I’ve always taken it as read that in the software world there are additional “perks” like saving and restoring exact state, and wouldn’t find that to be an issue.
I probably agree that auto-save (or intuitive saving) on hardware Random8 would be nice, you could probably email Befaco with this as a feature suggestion, it might be possible?
I try to maintain this here, but may be omissions (contributions welcome!). I’ve added the point about saving:
Finally if possible, is it OK to keep feature requests/bug discussion in the development thread - I appreciate not always obvious but can be useful to keep this as high level “enriched changelog” Befaco modules development blog