As long as sufficient care was taken in rolling out the hard fork to make sure that near consensus was reached before the change is active, I'm not opposed to this idea. On the other hand, I haven't yet looked into the other solutions people are suggesting (if any) to deal with malleability, so I'm uncertain if anyone is suggesting any methods that don't require a hard fork.
The plan is try to identify all the possible sources of malleability and define "canonical" transactions for each case.
If a single one is missed, then it doesn't work.
The advantage is that it is a soft fork.