It really depends whats the use case. There are a lot more efficient ways to run Chrome than usus is running it.
If speed is a concern, then usus should export an interface that allows to spin-up Chrome and re-use the same instance for multiple renderings. See this issue https://github.com/gajus/usus/issues/9.
If the sole intent is rendering of the page, then I recommend having a look at https://github.com/gwuhaolin/chrome-render. It provides a lower-level abstraction.
Otherwise, please contribute your use case to the usus issue thread and I will work with you to define an API.