Thanks for writing this Zakary!
It sounds like the problem you have is with your client management, not with your design artefacts.
Wireframes are a design document — they describe a point in the process, and are used to guide discussion and help communicate ideas. They should not “capture a user experience” or set anything in stone. Whether it’s a napkin sketch or a motion prototype (and whether you want to call them “scamps”, “mockups”, “sketches” or “prototypes”), they are used to help other people understand the ideas in your head. Combine this with the ideas in other people’s heads and you’ve got yourself a design.
We’ve all been in the situation where clients think wireframes are finished designs — but this is down to you to better educate your clients and stakeholders. Push back on account managers and producers that want to expose the client to your design process; or better still, involve the client from the beginning so they aren’t desperate for details by the time you’re finally ready to show something.
Ultimately wireframes are a tool, and it’s down to you whether or not you want to use them. However, it’s important to be able to properly identify the flaws in your design process rather than assigning blame to the tools.