Are you talking about XT/Classic style contentious hard forks, having a backup plan to change the PoW if necessary, both, or neither?
Contentious is not the same as absurd.
Note this is not a vote for anything in particular and should not be taken as such.
IMO, changing the PoW is not something to be done except as a last resort to protect the blockchain from a ~51% attacker.
But in a doomsday scenario, with an ongoing contentious hard fork causing unacceptable risk of catastrophic consensus failure, I'd appreciate having some good 2nd strike options having been presciently filed away on the shelf for future consideration in exigent circumstances.
It's like having a fire hose behind glass. Not a good idea to play with most of the time, but if there's a fire then it's time to break the glass and deploy emergency countermeasures.
In your opinion, is Bitcoin married to SHA-256 like it's married to other control variables like the 21e6 coin emission schedule, 10 minute block target, and 1MB blocks?
Is there a better way to resolve a (messy, scary, dangerous, mutually destructive) fork war than by one of the chains moving to another PoW?
I don't see Bitcoin as being defined by SHA-256; IMO the particular PoW (while carefully chosen as the best fit for the job) isn't an intrinsic feature of the Nakamoto Consensus protocol.
Is there something special about SHA-256 that other functions cannot do as well or better?