Yes for the first afirmation but only during boot process for a short time.
Also yes for the second one but module solution is easier to maintain and again work for all configuration, including launching Atmosphere with fusee.bin witch is not...
Easier to update a simple module than sig_patches witch have multiple files in multiple dirrectories. And you're right, the module could need some updates to match with new firmwares but for loader patches at least don't need them, also true for...
But with the module you don't have to regenerate the patches, for loader patch you can change or even rebuild Atmosphere without having to change anything else. It's not difficult to rebuild a new loader patch but with the module no need to do it...
The module apply the change on boot, no need to activate it again cause the system is patched. This module have only advantages against classics sig_patches because it doesn't take any memory to be active, it apply patches with patern witch is...
Don't need to use sig_patches or a fusee.bin modified, just use Sys-patch, it's easy to use, more flexible and now largely tested solution witch work perfectly in every contexts.
Thanks for the git share, more simple to follow.
Just a note, the "ES6" patch should be changed to exclude firmwares higher than firmware 17.0.1, like that:
{ "es6", "0x.6300...0094A0..D1..FF97", 16, 0, mov2_cond, mov0_patch, mov0_applied, true...
hahahaha I'm half way through a bag off my Volcano and my tolerance is way down because I haven't been smoking much lately, so I was a little slow to catch that that was what your angle was