Yes, that is what we thought as well, but it turns out that the there is still a delay between the load balancer controller registering a target as offline and the pod actually being already terminated. We did some benchmarks to highlight that gap.
Damn it, now you've made me paranoid. I'll have to check the ELB logs for 502 errors during our deployment windows.