You still can add a post response filter to update some statistics table after you send out the response to the customer to keep latency low and pressure on db low too.
Still very few companies need something like this.
Than you don't need it if you don't see the advantage.
You normally do lots of API requests while you are logged in. To services and to download an image for example.
You make sure the current jwt is valid for a few minutes and hit only the database with the refresh token for example.
Only in worst case you really need to block a token and it might be much easier to sync those few tokens in your system into some local cache and let them expire automatically (because you know when they expire as it is contained in the token).
But yes if all of this sounds complicated, use sessions and a distributed redis for your session or just the database.