Yeah, using Bootswap/Cauldron for bypassing downgrade protection is like using a chainsaw to cut a steak. While technically it will work, you're far less likely to lose an arm if you just stick to a knife. While the chainsaw has its uses, the knife is much better suited for something simple like steak.
To further the analogy (for no good reason (please don't put me on a watchlist)
), the TSA is going to be upset if you try to take either onto an airplane, in the same way that TI wants both bootcode exploits and downgrade exploits banned. Like the TSA, TI is also hilariously incompetent at enforcing this, and while it's much easier to keep the chainsaw off of a plane than a dinner knife, they still mostly rely on people fearing the consequences of breaking the rules rather than ensuring they can never be broken in the first place.
As I've stated previously, I won't be publicly releasing or even publicly disclosing whether I've developed an update for BootSwap for 5.6.1+, barring some major change in conditions, such as the CabriJr bug getting broken by an OS update, or on the off chance an updated Cauldron is released. I also won't release any downgrade tools until arTIfiCE gets broken. However, there's so many security holes in the OS it's not even funny, so I'm sure anyone familiar with assembly could write one in an afternoon at the moment. Right now TI seems to be relying on a implicit agreement that the community won't release a downgrade tool in exchange for not breaking the cabriJr exploit
, so I doubt anyone else will release one, either.