Thats the theory, if you remove device driver folks, how many really works on the Linux kernel ?
While I don't have time right now to actually go and count the number of distinct people involved, that's a lot of hands that have touched that source file over the years. And this view's only showing the changes that make up the current version of that file-- there are authors not credited there because their code has since been overwritten or edited by someone else.
[1] https://github.com/torvalds/linux/blame/master/block/bio.c
At that point one is comparing apples and oranges.
If it's not performing well for your typical users using typical systems, it's not performing well. Those systems aren't going to change.
Those who engineer the system need to just work around the system specific limitations. Like a virus scanner.
For instance, metadata reads on the filesystem are much slower on Windows than Linux, so it takes much longer to do the moral equivalent of "find /"
Circa 2003 I would say the Apache Web Server ran about 10x faster on Linux than Solaris, but that a Solaris mail server was 10x faster than the Linux server.
Turns out that Linux and Apache grew up together to optimize performance for the forked process model, but that fsync()-and-friends performance was much worse than Solaris at that time, if you want to meet specifications for reliable delivery.