One of the interviewers was augmentative and combative in their line of questioning as if they were playing "bad cop". I won't go into details, but I was given a hypothetical engineering situation that just wasn't realistic in my experience and tried to explain why, but they would not take no for an answer.

I've been on the other side of it, and your approach can come across as childish, like arguing with your math teacher that billy couldn't have eaten 4/6 or 2/3 of the pizza because he'd get sick.

It's a _hypothetical_. The problem needs to be constrained because realistic problems often either 1) have standard answers that don't require real thought or 2) are too hard to solve in an interview. Asking how you'd solve some problem on a CPU that doesn't support multiplication or something shows whether you have skills that could transfer to solving real problems but can be asked more quickly.

You don't know the specifics, but I can assure you that this JS developer did not know the specifics of the iOS development question at hand.

It's easy to purport a sense of theoretical superiority from your side of the table, and answering an unrealistic question doesn't mean that employee will deliver you real value over time. In fact, they may hold you up and waste more of your time because this "yes man" will spend extra time determining what's clearly a waste of time is in fact a waste of time.