I think that the default tripwire config (and definitely the default samhain config) includes monitoring new files in /etc, so at least there's that protection. Unfortunately not many people use those applications in real deployments.
Hmm, I have not encountered a suid login. Since login runs passwd, and passwd uses pam, and pam is heavily based on demand-loaded libraries, that would be rather hard and big.
Static shell? Sure, sash. Also helpful when ldso or libc is busted via non-rootkit means.
Some programs (such as login), are already statically compiled to prevent this exact thing from happening.