If your api is not asynchronous, then any expensive call is going to lock the entire application which is bad and also why I won't be using this library despite the actual underlying implementation being much faster.
Did you measure the impact, subtracting harder development and run- time? Do you like to code in all hard ways before you meet any problems? Is sqlite a key performance point in your app? (Why not async-pg then?) How many requests per second do you have at average peak hours?
It certainly isn't the case for nodejs.
One could wonder whether that's an issue when IO are fairly short & strongly interspersed with code being run though, the overhead of switching tasks could be higher than the IO you're synchronising. I guess whether this is a good idea would strongly depend on how you're using sqlite (aka do you tend to make lots of very simple requests with small output or a smaller number of more complex ones).
IMO one of the core observations made by Dahl and the other Node.js folks was that this is very very rarely the case in modern web applications. Most webapps either a) spend the vast majority of their time waiting on IO, b) have non-IO code very regularly interspersed with IO operations (making event-loop based interleaving based on IO boundaries more useful) or c) both.
As a result, Node.js was built with the single-thread/IO-bounded reactor model. I think that this, along with (and perhaps even more than) its choice of language syntax, drove the platform's adoption. It means that code doesn't need to think about thread safety, and that there is only one IO model: asynchronous by default (yes there are exceptions, but they're a minority). That lets users get a lot of scale for free, provided their workloads meet those criteria.
For example, that almost everything in Node is asynchronous, like in Go, is one of its best attributes. Compare that with the state of things in Java, Rust, Python, and most other languages if you decide you want to use the reactor pattern.
If you don't want an event loop, then you don't use Node. But not blocking the event loop is not "religious." It's how they work.
Who the hell decided that making sqlite asynchronous is a good idea in the first place? Node is so religious on async that creating everyday transactioned apps in it is PITA that never ends.