Well, my use case is that the business doesn't want to set that value more than once. The entire app is designed to stage the exact object and all properties into next environment. I don't see why all the sudden we'd want property values on a particular object to reset when we stage the object.
I actually don't use Kentico very much for the end user. I am usually doing development work on items for my business. However, I do stage objects all the time and I don't ever want their property values to reset when I stage the object. I can't think of a single case where I'd want to set an int value after I stage it; that would just take more of my precious time, as I'd have to login to another server, click stuff, then set the value again through the frontend. I'd advise you to add this as an option if you want people to keep using your software; as a professional developer myself, I can tell you this wouldn't be difficult to do (if I had your source code), and would keep your customers happy.