Confirm/Cancel (like Yes/No) for dialog buttons has been known to be confusing and detrimental for decades now. The button names should always describe action to be taken, not a response to the text above.

My point is that the operator may be genuinely confused by a poor interaction model. Removing that interaction model entirely is certainly an option, but it's not clear that comparing "no dialog" vs "bad dialog" is a strong argument for "dialogs bad, better to have none" - you don't have data for the "good dialog" case, which may be better still.

I remember being confused as a kid by "Yes/No/Cancel" when the computer asked "Do you want to save the changes...?" because I couldn't figure out whether "Cancel" meant "Yes" or "No" and why on earth would one have a third option. I then realized it meant to "cancel" my intention to close the file. I had been confused because I thought it meant to "cancel" the computer's intention to ask me.

Also, I was that obnoxious kid who, after asking someone a yes/no question, used to add "Yes/No/Cancel" (probably to highlight my perceived absurdity of that button).

Like the "Cancel subscription" dialog with options "Cancel" and "Cancel"...

UX Design is hard...