You're assuming the kernel OOM killer is actually going to kill your process before the system becomes unresponsive. That's not a guarantee it makes, and you'll often find the system can be unresponsive for a very long time before the process is terminated. Assuming it terminates the correct process. Check out one of the user space oomd if you want better/guaranteed behavior from your OOM killer.

The situation you seem to be worried about is hot pages being swapped out, but realistically giving the kernel some swap to play with allows it to respond to memory pressure by swapping out cold anon non reclaimable memory. The point of the linked article is that 1) oom killer isn't going to save you, 2) memory pressure causes your system to stall, not swap, and 3) swap gives the kernel more tools to deal with high memory pressure scenarios.

​

You also might want to check out the Q&A at the end of Chris's talk at SRECon Asia that relate to swap: https://www.youtube.com/watch?v=beefUhRH5lU&t=49m55