I think it is appropriate to reopen this question in a few months or even next year.
I agree with everything you just said.
The software is awesome, easy with a library and impressive rendering.
The cofiguration is limiting, the rendering of Mmde X has the same atmosphere as the rendering of Mr Y.
I regularly test TwinMotion and each time I reject its use.
From a development perspective, Epic has just acquired TwinMotion.
Look at the roadmap to understand that TwinMotion is not yet finalized.
But some features currently in beta are very promising.
There is now native synchronization with TwinMotion for Rhino, limited but working fine. Can also export to Datasmith.
TwinMotion / UnrealEngine integration is in progress. The TwinMotion library is being exported to UnrealEngine.
And if we are to believe the announcement made by EpicGame on UnrealEngine 5, we should be able to use UE without the specific constraints of optimizing video game platforms. No more worries about UV channels for lightmaps and no need to wait 10min for the machine to precompute the light each time the scene is modified. With Lumen.
(Don’t tell me about EU Ray-Tracing. If you’ve used it, you know that taking the time to import your model into the EU and the performance of Ray-Tracing EU provides little more benefit than other Ray-Tracing rendering software.)
When all this is finalized, it is possible that the Rhino->(TwinMotion->EU)->Image/Video workflow will be really simplified.
NB. I just saw for a moment that the version is now accessible.