I think that someone who's radically opposed to any use of AI is simply a poor developer.
You said it yourself - you have the knowledge and ability to know what to ignore and keep what makes sense, but that's because you spent years actually writing and understanding code.
The magic wand of AI is absolutely wreaking havoc with juniors engineers' ability to understand complex code bases and software engineering fundamentals. How will the engineers of tomorrow know what to keep and what to reject if all they've ever known is "you are a principal engineer. read this Jira ticket and build a solution. ultrathink".
I think that junior engineers can learn from AI, but the corporate setting isn't the best place for self-learning from AI. There's a lot to be learned from the average advice from the better AIs, as long as they are trying to understand the feedback. Please note that for these engineers, AI is replacing the old copy-and-paste from Stack Overflow. At least with AI they can dig deeper and ask questions.
I used to think there was no downside, but now I think there is.
You're developing the skill of choosing things out of a list to use. Your skill of creating that list is withering because you've offloaded it.
Now, I won't deny there's power in an AI code review, and for many people and occasions that tradeoff is worth it. For me, as well. But I'm convinced from my own experience it is a tradeoff.