No, but that does sound like a good idea for me to spin up and test. I like it because now I can put databases on my webhost which gives me unlimited MSSQL space.
*Edit*
I was also curious so I did some crude testing and some research:
Turns out, depending on your use is how you should decide which to go with. According to SQLite Org - When To Use , SQLite is not made for High Concurrency uses. This means if you have multiple programs writing to the same SQLite database, SQLite is not always the best options compared to products designed for it like MySQL and Microsoft SQL Server.
"SQLite supports an unlimited number of simultaneous readers, but it will only allow one writer at any instant in time. For many situations, this is not a problem. Writers queue up. Each application does its database work quickly and moves on, and no lock lasts for more than a few dozen milliseconds. But there are some applications that require more concurrency, and those applications may need to seek a different solution."
For my personal use, I plan on putting my databases up on a host, and have multiple servers talking to the same database, so for me, SQLite could become a bottle neck. So it really depends on your use, preferences, maybe depending on hosting like mine, other performance reasons, etc.
Should also note, you can setup MSSQL and MySQL servers on a different machine than your game server so you do not use up resources for your game server.
Below are some simple crude speed testing for single use.. ie 1 database, 1 program. PC Specs:
CPU: i7-8700k
Memory: 32GB 3000 mhz GPU: 1080-TI Storage: M.2 PCIe Samsung 960 EVO 500 GB
TIME IN SECONDS