Make sense? No that's wishful thinking, and there is proof.
The proof is literally on the switch 1, entirely reverse engineered. They reused the same OS, again, especially the cryptographic methodology....
lack of knowledge and/or ignorance is not going to alter reality, unfortunately.
even game updates are rightsid encrypted, though nintendo appends the titlekey for that to the public ticketbin (not signed), whereas game files themselves are appended signed to the private ticketbin.
your "sigpatches" remove the signature validation of the ticketbins, letting you insert rightsid titlekeys yourself to the public ticketbin, which means we have as we got the certificates and ticket by querying nintendos servers themselves pre-dauth* and after dauth, that is how you can install games that you haven't paid for in first place on the switch 1.
(* pre-dauth == edgetoken system wasn't initially implemented, it was implemented after widespread use of some guy named thomleg's ssl certificate (your "prodinfo") to download game files, without a titlekey, in large scale by users, using what used to be called nut, on their pcs, alongside game updates, without any protection, aside from the obvious rightsid encryption, which updates gives you automatically, but game files required others to "share it with them", i.e. shared titlekey list from others who bought it)
(this is why you don't receive game updates on a banned switch, they are rightsid encrypted, thus locked behind edgetoken/edgeauth/dauth requirement)
also subsequent note; several people including myself, have attempted to prod at the switch 2 AWS endpoints, and sacrificed one nintendo switch 1 ssl certificate in doing so, to verify that it is indeed the same, and they didn't change much. Unfortunately it only yields metadata and not actual files( in other words, the switch 1 can query for switch 2 game titles, but will only receive metadata information about them, i.e. the kind of data you see in eshop, the description and pictures)