Usually I don't think it's necessary. My yes/no questions are something like "Okay, so we need to put some more info into that file since that's what exported to the billing database, is that correct?". When I don't know something, I try yes/no questions at first. If I get "yes", then it's resolved. If I get a no, I will ask open-ended questions to explore the subect. Once I think I have a correct mental model ready, I will ask yes/no questions to validate it. If I get a no, then it's the cycle again.

For the "Is it raining outside", I honestly don't know anyone that would just tell me "no" when there's hail outside. For the "Do you like Vi or Emacs or something else?", it would be "What text editor/IDE do you use? Why?". "Do you like Vi or Emacs" by itself is not a yes/no question, it's a "what box are you in" question. For "Do you want to hang out for a coffee or something else?", that would be something like "Do you want to hang out at <TIME>?".

An important part for me is that in yes/no questions, no are supposed to be the exception. In my mind, when I ask them, it's not a 50/50 chance. It's more of a 80/20. If it was a 50/50 chance, that means my mental model is not precise enough.