1. I do not want my production instance to shut down for WHATEVER reason. This is just not an acceptable risk for most businesses. The only time a DB can go down is something goes wrong.
2. As an engineer, I understand that 3 counters that are not accurate aren't a big deal. I can even look into the source and see that they really do as you say. Justifying this to a security org will be a complete nightmare, as most security orgs in enterprises are staffed with barely technical folks masquerading as "security".
So, it seems like a pretty good way to coerce enterprises to pay up while letting hobbyists continue using it. Very smart, I wish you the very best!
Make it available and simple for hobbyist and small companies, ask money to who can afford it to sustain the development.
Right now I am busy with releasing the v2, but after that I should definitely do some more marketing.
Anyhow, to give you an order of magnitude, on memory data storage we reach ~80k inserts for second. On a machine with 1vCPU and 3GB of RAM, a 15$/month box from DO.
The interface will be either HTTP or Redis protocol, you create your database, and daily I will back it up on S3.
(If interested you can subscribe for updated here: https://simplesql.carrd.co/
[1]: https://redisql.com/