Wasmtime's fuel metering makes applications horribly slow.

Is there a better way (NOT epochs) to deterministically track fuel usage of applications such that the fuel is incremented after certain blocks of code instead?

Because in blockchain based applications, we don't NEED to stop the execution after an exact fuel count, we need to overall stop it after a limit (even if it is slightly over the limit).

The performance would be improved significantly is this can be implemented or can be enabled through some configuration.