One of the things they're planning next is to replace the current kernel VT implementation with a userland terminal emulator that depends on systemd, so you won't even be able to boot with init=/bin/bash in a pinch because without systemd there won't be any terminal to run it on anymore. No idea how people will be expected to diagnose and fix issues that break boot at that point.
Pick a 'usb stick' distro of choice (my choice is usually sysrescuecd) and boot that image off of media or virtual media if you have one of those remotely managed systems. Though it sure would be nice if said systems could pull the image off of a mirror local to the DC.
Alternatively, build a similar rescue option in to your boot menu; if that's broken you've got no choice anyway.
USB rescue distros are nice, but that assumes you have a USB stick to use and already had the rescue distro installed. That doesn't help when you are trying to fix some failed update late at night with the computer in question being the only hardware available. Contrived example? Yes, but I've been in more or less that situation a couple times in the past and was very thankful that init=/bin/bash worked as a fallback.
// yes, most of the time I just put fallback/rescue options in the boot menu
