I apologize for the way my tone came off -- I didn't mean to sound bullying; and by "you" I mean DocuWare, not you personally.
In my opinion, when a customer demands something, that resides on the spectrum of "desperate times". It is not DocuWare's call -- it is the customers'. I'll put it this way: where I work, if a customer asks for something, we do it unless we have a very good reason not to that we can help the customer understand. Otherwise, the customer goes somewhere else. It would probably be worse if we said we listened to the customer's voice, hundreds of customers told us what they needed, and we ignored it. You ask which is more important, data or a timeout -- I feel you are missing the point. Over 200 customers are wondering why data integrity and session timeouts need to be mutually exclusive.
I am not sure who the Product Owner is on this thread. Tobias? There is nothing to indicate his status if that is the case, so I honestly didn't know we were hearing from a "Product Owner" (I always thought Tobias was a support person like yourself). Not sure it matters, though, since his responses stopped coming even after people continued to explain their business-case need.
I agree that a comprehensive workstation lockdown SOP would be better for end-users overall, and named licenses cover concurrency issues, but that doesn't change the fact that the customer is always right. That is, unless DocuWare can more clearly explain the downside of keeping the timeout solution in play -- something no one (not even a Product Owner) has done yet.