Re: why people are using the word "dead" regarding code annotations:
Without getting into a discussion about the title being clickbaity (I think it is), the paper's point is still entirely valid. Yes, you can ignore the annotations for production builds as you point out, but then you don't get the soundness guarantees at the edges of untyped and typed code, and that's the entire crux of the paper.
I'm not sure why people keep using the word "dead" regarding code annotations. They're easily stripped out for release builds and clearly provide value in many debugging and maintenance scenarios. And yes, like everything else in the static vs dynamic debate, there's no free lunch.