Yes, in the remote device setup table. The output of remote device set-up page should be configured so its output goes back into the controller. You set a transmit flag. Once you’ve bound it to a VST control in the DAW, it should transmit feedback to a controller accordingly. Note…to bind a control directly to a VST/VSTi plugin’s control from this map, you’ll need to be sure such a plugin instance is loaded into the rack or an instrument track first. That remote device page should give you access to any VST parameter in the system, as well as a quite few things in Cubase that don’t have VST automation lanes such as macros, menus, and more.
I personally like to route it all through a MIDI track into a virtual MIDI port, then from the virtual port to the Cubase remote device map, and then back into the controller unit…that gives me the ability to optionally record/edit/automate controller movements via MIDI track as well (can bounce it to a true VST lane later…but love those global and logical editors, retrospective recording, MIDI track inserts, and multiple track/lane management abilities that MIDI tracks provide).