The fidelity of Wireframes has always been a question among designers. When dealing with Clients, low fidelity wireframes mean unwanted questions about things you are not currently focusing on and high fidelity wireframes mean unwanted questions about the details like color and position.
A good way to overcome this problem is to understand what is the critical property you want to convey through this wireframe and that property could be as small as color of a button, or as big as the date picker on a travel website. Once that property is decided upon, it is useful to break down the wireframes in terms of those pieces.
What I mean is, if the most critical property is color of header for example, you create several wireframes just to convey the colors and choose one. If the next critical property is footer, you create several wireframes just for the footer.
This process sits well with agile framework. During my internship, we worked in development cycles of 2 weeks, each period called a sprint. In each sprint, we would decide one property to focus on. As the designer on the team, I would create several low fidelity wireframes first to discuss with the manager and get feedback and then convert them to high fidelity to show to the client. Once the wireframes has been selected and approved by the client, we would move on to the next property in the next sprint.
Did the client ask questions about other properties you were not focusing on? YES. But its easier to answer if you have wireframes for those properties or plan in the coming sprint to show those properties. And since the client already knows the property being focused on in the current sprint, diverting questions are very very few.