Thank you for pointing out the hack. I will definitely take this route for now.
As for the official workflow, well, I do not want to endorse a workflow with CFD calculation for every time step either. Typically we run CFD only for one or two worst case scenarios, with the intent to verify whether or not the AC system can cope with all the loads (convective + radiative).
What we need is an object to update the PMV calculation only for those time steps (or even one time step at a time) with a new temperature and air velocity values.
Note: CFD for every time step has been implemented in ESP-r, although it was for calculating the convective heat transfer coefficient, not for comfort. There is a “gopher” run, a quick CFD simulation, that runs every time step that will decide whether or not to call a full CFD run for that time step. If the gopher decides the flow regime is similar, then the full CFD run will not be invoked. EnergyPlus has a similar capability, though, the CFD code is not part of EnergyPlus. Just to point out that CFD for every time step is not unheard of. But I really do not see we are going in this direction.