Hey, I'm glad you found the information helpful.

If you decide to use your own avb custom keys (meaning that you are the only person who can install cfw - this means that google, graphene, etc would fail to install as they aren't signed with your keys).

You can then use tools like Custota to allow you to have/distribute your OTA (over-the-air) cfw updates.

Why would you want to do this?

Well, for sometime I was running a rooted version of graphene w/ magisk (as I wanted "real" offline backups). This means that I needed to "sign" each release and the official graphene updates. The process was a bit tedious, but well documented.

The upshot of custota being installed on my device, was that I got a notification when I had a new self-signed update available... and the release/install process was entirely under my control. ...and if something borked, I could "rollback" to the previous version (tbh, nothing did bork, so I didn't actually need to try this).