Based on my understanding, sys-patch and KIP-based sigpatches are two different ways of applying sigpatches. You don’t need KIP-based sigpatches if you’re using sys-patch, since sys-patch applies them dynamically at runtime. That said, Shise’s guide still uses fss0 with KIP patch lines and doesn’t mention sys-patch, which suggests it’s relying on a boot-time, KIP-based sigpatch approach rather than a sys-patch-based setup. Boot-time KIP sigpatches are more self-contained and deterministic in the sense that they don’t depend on a runtime sysmodule loading, which makes them a reasonable failsafe baseline for a general guide.
The guide appears to prioritize: “it boots and works every time,” minimal moving parts, and no dependency on a userspace service loading correctly.
- Sigpatches = disable Nintendo’s signature checks
- KIP patches = one way to apply sigpatches (at boot, via hekate_ipl.ini)
- sys-patch = another way to apply sigpatches (at runtime, as a system module)
