If you type both brackets at the same time, sure that involves 3 separate key touches instead of four. However, you would then need to move the cursor to be between the two braces to keep typing. That is the fourth stroke.

Or you add the closing brace after writing your code block, in which case you have to let go of the shift-key while typing the code block and holding it down when typing the closing curly brace. Whatever way you choose, you still end up with four keyboard key touches.

That your IDE can put in closing braces is irrelevant to the discussion, as the argument was never "fewer keystrokes makes end better," rather the argument was that there is no keystroke advantage to braces. You cannot use number of keystrokes as an argument to why braces should be preferred over end.

A modern IDE invalidates that claim equally well as it can insert an end as well.

My key argument for why should prefer end over braces was never about keystrokes but about how end more easily visually identify blocks of code, and how you ration the use of braces which you have in very limited supply. If you use curly braces for code blocks it means it will be harder to use them for other purposes.