I hate to be that guy, but take it from me as someone who recently studied UX, like, literally and on a PhD setting, where we learn all sorts of important principles regarding the scientific method, biases and whatnot.
When it comes to such deep-level functionality, such as basic navigation, it shouldn’t be the case where people here, who already enrolled on a Beta, should dictate how your app should work, because there’s already a huge amount of self-selection bias going on. Beta testers who are going out of their way to test your app for free, and not random paid testers taken out from the street, will generally be more tolerant of non-standard UX behaviours that will leave the latter scratching their heads. Also, and ideally, your tutorial should feel more like an afterthought and explain some truly novel and unique concepts like pinch-to-add-items-in-between, but not essential navigation gestures (not tapping a tiny, unlabeled target), which even a child should be able to figure out on their own.
Back to numbers, and TL;DR: if you get 1% of power users – us – complaining, that may very well conflate to 30% or more of regular users hating it upon release and not even bothering to tell you why (most regular users hate questionnaires and can’t be bothered to give out reviews, especially if they’re offered a free trial activated through an in-app purchase). You won’t just be catering to those old Clear users relearning to use the new app and unlearning the muscle memory acquired from the old one, but also to iOS users at large, constantly fighting an ongoing and very much alive muscle memory from using all other apps on the platform daily.
And that includes… me! In my case, I’m a bit of a hybrid because I haven’t been using either of Clear’s versions much lately, but I had used the Beta some time ago (including this latest update), then I went back to old Clear, and today I saw the update to the latter and, since I had completely forgotten about how to do it on new Clear, went about trying everything other than the non-standard and non-discoverable method you came up with, thinking the app must’ve been broken, that the migration from the old app (which it offered to do again, and I accepted) had gone wrong and corrupted its database, etc. I felt like we were, together, a textbook case that should’ve been recorded and used in reference books as an example of what one should not do, and I consider myself an advanced and adept mobile and desktop OS user. If I, of all people (an advance Beta tester for much larger companies and professional apps, with signed NDAs and whatnot), could be made to feel stupid while using yours, or think it was outright broken, I can only imagine how some of my older family members would feel and what they would think if they picked it up after a few months of not using it and weren’t, thus, offered the intro tutorial again (by the way, the little mental exercise I just did can and should be fleshed out formally in the way of creating actual personas; it’s supposed to elicit more empathy on developers and help them figure out – yes, without necessarily even having any contact with said personas, by way of anticipation and simulation – shortcomings in their offerings)… 
Interestingly, even old Clear suffered from this problem, and it seems they’ve implemented a non-functional reaction to edge-swiping, as if to tell the users that “nope, that doesn’t work here” and nudge them towards the swipe-down-to-go-back one, but hey, at least those gestures were fun (aural feedback plays a huge part in that, but the gestures themselves are, too), and you did get constant visual feedback on what they did, kind of like a permanent tutorial.
You now have a prime opportunity to “fix” Clear, but you’re clearly choosing the worst possible path, and it makes me fear for the future of the app. It’s almost as if you were given the keys to an 18-wheeler and you just have a regular car driving license, i.e. that you were made custodians of an app that did make use of novel and risky UX without really understanding what going down that route entails and how miserably it can fail if not done properly. Please dust off the ol’ UX manuals and go back to ground principles, because it seems like you’re missing the forest from the trees and getting too cavalier here, by outsourcing responsibility to your testers instead of doing a proper analysis of what is going wrong and extrapolating from there… Data gathering can’t just be quantitative, but also qualitative, and if an issue is serious enough (and in this case, it is, and I guarantee you that I never write these passionate rants about, say, a misaligned input box or something – that’s what screenshots are for
), 20% of direct complaints on core functionality is waaaay too high of a number to gamble the future of your app on.
Anyway, back to the matter at hand: the home bar doesn’t serve any special purpose on any other iOS app that I can think of, and if it can indeed be made to do something other than its OS-wide home button replacement and app switcher functions (and also the off-by-default Reachability setting; that swipe-down gesture to move the top of the screen to the middle, while not as elegant as the tapping home behaviour you came up with may indeed be, is at at least universally useful), please make it optional and in addition to, not in replacement of whatever default method you’re using, precisely to prevent scenarios like the one I’ve just described, when a user may have dropped the app for a few months and completely forgotten that whiz-bang, custom method unique to it…
By the way, I can guarantee you there’s a HUGE swath of potential Clear users, the ADHD persona – of which I’m an example of, yep, diagnosed and all –, who will have bouts of productivity and use a list-making app for months, then drop it, then use it again, rinse and repeat, because making lists is an actual and vital coping mechanism and productivity tool for us – what I’m trying to say is, A LOT of search results for Clear will literally be served to ADHDers after their therapists and psychiatrists recommend that they make lists of some sort –, and forgetting about stuff and having radical fluctuations in productivity and commitment to certain tools and processes is sadly a common theme in our lives as well…
And do you know why I picked Clear, and potentially other ADHDers might, too? Because of its “gamification” and aural feedback, which copy the same dopamine-kick-giving processes typical of mobile games, and even social media apps, except used for doing good and helping people instead of for exploiting addiction, pay-to-win IAPs, their personal data and time, etc… It makes our coping mechanism fun instead of boring, which means it’s more likely we’ll check our lists than doomscroll or waste our time on some random app… That alone should be grounds for you to keep the non-standard swipe gestures (and restore the arpeggio notes!!) of old Clear instead of forcibly making it more standard (and boring) and use edge-swiping exclusively, or something. Maybe I’m dopamine-splaining you your own app, so please forgive me in advance if that’s the case, but it just comes down to these bad signs that make me think you’re not as experienced as, or didn’t communicate as much as you should with the old Clear team (I seem to recall reading somewhere that said gamification was a HUGE and deliberate part of the entire ethos behind Clear, down to the vibrant colour palettes), so please correct me if I’m wrong and prove me otherwise with future updates.
On that note, and before you think I somehow hate what you’ve come up with here (I don’t): your idea is indeed great for large screens, and can indeed be a boon for users with mobility issues who may be unable to tap and swipe (that’s the thing with neurodivergent people and institutional – and real – empathy: we also tend to become little ADA-compliance and Accessibility encyclopaedias, especially if we work in the Design field), so you might as well submit it to Apple as a suggestion for inclusion on iOS and iPadOS; as developers yourselves, especially if your app ever explodes in popularity (and it hopefully will), I’m positive you’ll get better access to the iOS dev team’s ears than the general public. But I guarantee you that should they implement it, there would be some sort of visual, UI affordances if it was to become kind of like Android’s old physical back button, such as half of it being arrow-shaped or something, or being part of an unskippable, system-wide tutorial during device/OS setup, and obviously be available on ALL apps and become part of a lot of users’ muscle memory (and, still, I doubt that it would completely replace visible back arrow buttons on title headers). Discoverability is key, and so is muscle memory and OS-wide UX compliance, so please be patient and don’t try to forcibly out-Apple Apple.