Thank you for your reply. This docker image is running in Google's Cloud Run service, so depending on traffic a cold start happens quite regularly. While 700ms is not the end of the world in this context, it is a bit wasteful comparing it with other technologies.
I've looked into what "octane:status" actually does, and it simply reads the process id from a json file and sends a kill -0 to the process. I've replicated that functionality as a simple shell command