Interim Solution for 17.1 patch problem - a suggestion

Since an unknown number of people have been afflicted by the 17.1 bad patch and since not all of them are getting good advice from customer support or coming here to get guidance; and since the repair is now an indefinite distance in the future, wouldn’t it make sense to develop a patch that checks to see if the customer has 17.1 and if so to return the application to its 17.0 configuration?