If they change the spec and certbot follows them, I doubt it will deprecate the non-google approaches. If they do something novel like enable multi-level wildcarding not just the terminal leftmost *. form, People might get stuck on how that works, but it would probably require chrome to change too.
mainly I suspect this is to pacify people inside GKE who don't like calling outside of the protected space to get certificates to exist.
