I want to use the Kano model to determine if a feature being added to an existing system is something that will be used or not
I'm not necessarily sure the Kano Model is the best tool to help you answer this question. For this I would recommend surveying users, showing them wireframes, or even building a quick proof-of-concept that you could demonstrate to request feedback.
Kano Model as an Internal Tool
My preference for using the Kano Model is to try to identify and prioritize the business value of new features. So I typically reserve this conversation with business stakeholders, such as project managers and product owners.
The way I tend to explain it is there are 3 categories: basic needs, performance needs, and exciters. Each of these categories must stack on top of one another. Meaning, we absolutely have to meet the basic needs before considering improving performance, or we have nothing. Then we have to have a product that not only works, but works well, before we can begin polishing it. I find this is a good technique for keeping the focus of a team, and ensuring all facets of the product get adequate attention.
Once everyone understands the Kano Model, and in my experience it is usually well received, we are able to answer a lot of these questions internally.
If the Machine Vision feature reduces your time to complete the task how would you feel?
If we know a feature will reduce the time to complete a task, we can already categorize it as a performance enhancer. The product already works, and we're just making it work more efficiently.
If the Machine Vision (MV) feature has no affect on time to complete the task how would you feel?
Improvements that have no affect on time or performance are often categorized as delighters or exciters. On our web-based products this is often aesthetic design upgrades. For example, a design team may want to begin migrating in the direction of a new style guide. The product works, works well, and now we are investing in improving the perceived value.
Kano Model Conclusion
By answering some of these questions internally, using the Kano Model as a guideline, it helps to stay on course for delivering a great well-rounded product. It helps avoid scenarios where a great UI concept is smoke-and-mirrors, while also helping to avoid creating a technically robust product that has poor UI/UX. It also provides stakeholders more information when deciding where to invest the team's time.