One thing many people overlook on ViewState is that it is defaulted to enabled on all controls, and in many cases it is not needed. If I was concerned about ViewState size, the first thing I would do would be to disable ViewState whereever it is not needed.
The solution discussed in the CP article, does not mention that ViewState must be used for controls where the user can directly change the value, such as a textbox. Unless you use some JavaScript or jQuery workaround and a bunch of query strings, ViewState is the way to get back the values a user has entered on the form.
So, the only place where the solution you are considering would be of value would be a place where you have an asp:Label or asp:Literal and are changing that value in server-side code in response to a button click or some other event, and need to make sure that the change is persisted over subsequent post backs.