Looking at the overall flow, and to which public it is aimed, I think most of the work done here can be reused, but needs to be decoupled into separate components, in the way described by @areusch in ([µTVM] Mini-Map: the µTVM Developer Workflow).
In that way, we would leave the door open for integration with other RTOS flavours, as well as keeping the separation of concerns to bridge TVM with more than only Zephyr.
From that perspective, tvmc continues providing an output that we can then plug into an embedded project, to be used.
I think would be very valuable for the end-user experience, and can be done despite all discussed here in a separate PR.
I suggest we reach an agreement on [µTVM] Mini-Map: the µTVM Developer Workflow, and then revisit the strategy here to adjust it accordingly.
cc @mjs