VIP Scaler II run-time writeable coefficients

We have been successfully using the VIP Scaler II with default compile-time coefficients for several years. Due to additional customer requirements we later (2019) tried to implement run-time coefficients, but were unsuccessful in the limited schedule available, and punted to compile-time alternatives as a necessary expedient. Now for new products/customers we are needing to try again, using a Verilog state machine in our code to write to the Avalon-MM control port at the start of each frame, e.g., as described in the Video and Image Processing User Guide, UG-VIPSUITE 2016.05.02, section 17.

We now appear to have everything ALMOST working properly, but are seeing distortions in resulting imagery which seem likely to be resulting from some possible scrambling of coefficient data, in/after the writing process (more details can be provided as needed).

As near as we can tell (e.g., using SignalTap, etc.), we appear to be properly formulating and writing the appropriate coefficients, but we aren't aware of a way for us to directly see how they are being received inside the IP. At the same time, there are concerns that the UG may not be very complete in further details of the writing process, and that it appears in some ways to be confusing and or self-contradictory.

We are wondering if there might be any additional documentation or other resources we might refer to or draw upon, if others might have been more successful in implementing a process of this sort, if there are any applicable errata for the UG (we have found no updates), and/or if there might be any applicable known bugs in the IP (and corresponding patches or workarounds).

We truly would greatly appreciate any help/verification/correction of our detailed implementation of that process which you might be able to provide.

(Note: The required label ("Interface Protocol - Display Port|HDMI") doesn't seem quite appropriate, but was the closest in the limited list provided.)