Jasonette can already operate locally https://github.com/Jasonette/JASONETTE-iOS/issues/48 so if it REALLY comes to worst (which I highly doubt), you still have no problem using Jasonette, all you need to do is store and load the JSON markup from the local bundle.
I guess a good analogy is a web browser. Unlike any other app development approaches, Jasonette works like a web browser. Web browsers can display different content and do different things just based on html/css/js. But it's a single sandboxed app that has expected behavior as a whole.
Check out the hacker news thread on this issue to see what really is going on. Not even react native people are influenced by this, it's just the rollout.io guys, which most people seem to agree that went too far https://news.ycombinator.com/item?id=13817557
TLDR: The problem at hand is for a company that actually engages in an actual problematic behavior. But even in the ABSOLUTE worst case, you can still use Jasonette simply by writing the markup on the local bundle instead of fetching remotely. Our main goal is not about bypassing the appstore. It's about expressing and building apps very easily.
P.S. BTW while all this was going on, a new version I submitted for Jason app just got approved this morning. Sharing just for reference.