43 years ago Emacs wasn't written in C or Lisp. It was first just a bunch of TECO code, and TECO was written in assembler (I still have the source on my bookshelf).
In fact none of the first three machines to have Emacses (PDP-10, Multics, and the CADR Lispm) supported C. (C was eventually ported to the PDP-10/KL-20 but C can't really represent those machines very well. C was really designed for a specific, restricted kind of architecture, one that is popular today).
https://en.m.wikipedia.org/wiki/Emacs
So, would you just say around 38 years and agree that 43 or 38 is pretty much irrelevant to my point?
I don't think emacs should be made any slower than it already is.
Then there is something wrong with your environment. Emacs has no problems with big files. It can have problems with very long lines, but big files shouldn't slow it down.
But, 2000 lines are really not that much. Usually problems on my systems start to show at >10k lines.
Not exactly related but with Emacs 27 will be distributed the so-long mode that could toggle minor modes that affect redrawing like "font-lock", "visual-line", "whitespace" when files with long lines are opened: https://git.savannah.nongnu.org/cgit/so-long.git/plain/so-lo...
The emacs developers will be very interested to hear about it.
It’s probably possible today to write an Emacs in a high-performance Lisp.
Elisp has no support for concurrency, for example.
“Some 359,000 lines of C code comprise its kernel, and 1,637,000 lines of Emacs Lisp take the rest of it.1”