Ridiculous. The argument apparently assumes that the only time spent in the editor is writing code. Not writing tests, or documentation, or email, or for reading code, or searching code.
So sure: if you only use your editor for typing in code, it's "not the bottleneck" to getting your code typed in. The problem is that if you're using you're editor like this, your editing skills are absolutely the bottleneck to doing productive development.
There's also the question how how that 100-200 LoC number is measured. They're looking at code that actually got checked in to the project they're looking at. I write less than that at work, but there's also an iceberg of code that wouldn't ever get counted. Iterating on multiple revisions before checking one in. Throwaway experiments. Side projects (the only reason I have them is that with fewer constraints they let me stretch my legs and code up a storm).
So sure: if you only use your editor for typing in code, it's "not the bottleneck" to getting your code typed in. The problem is that if you're using you're editor like this, your editing skills are absolutely the bottleneck to doing productive development.