Only thing I would change is that OSArmor is not a behaviour blocker, it's a post-exploit protection layer. It will only trigger alerts and block actions once they have been launched.Hard_Configurator and SysHardener are similar, they both tune Windows built-in settings to harden the system.
H_C is more powerful, but in my opinion is better for intermediate to advanced users; SysH can be used by anyone (even if it requires at least a basic knowledge).
OSArmor is a behavior blocker that works in realtime. In my opinion is very good because it's very configurable and doesn't bother you too much with popups.
If you have CruelComodo you don't need any of them.
All the programs you mentioned are very good.Neither Emsisoft?
so either SH+OSA or H_C are in either case not needed and redundant with the above software?
No, it doesn't work like that. OSArmor works with pre-defined rules. For example: blocking outbound connections to X processes or denying execution of X process. If malware tries to perform any action which a predefined rule has on its configuration, it will be blocked. It doesn't scan the file nor it scans its behaviour, it just compares blocks the action according to the rules. If a new malware includes an evasion technique or a new way to infect you without using a process or action blocked by the loaded rules, OSArmor will just watch it happen.what is the point to aleft after a ransomware was able to encrypt your disks?
Kind of, but here's where behaviour blocker, heuristics or IA modules come into the scenario. Although, most suck. Yet you have a couple of good ones like System Watcher or SONAR. But in most cases, zero day malware pieces will most likely get you crying.this is what every AV does when doesn't recognize a new threat
I have Windows Defender with CruelCommodo. I tried to add SysHardener and OSA at some point and got problems I didn't know how to solve mostly limitations like OneDrive stopped working. Sometimes a problem arises a month later and it's very difficult to pinpoint a setting you changed.
Macrium to the rescue!. But I kept the firewall rules of SysHardener.