As I said...normal automation is not available in a V-rack, (I think, check motunation to be sure). But midi automation can be.
Automation has to be handled on a "timeline". When you use a chunk sequence, it has a timeline. So when you are hosting the instrument directly in the sequence, you have access to program automation for every parameter of every plugin you are using in that sequence.
However when you put a plugin in a V-Rack, then the V-Rack doesn't have a timeline and for whatever the reason DP does not (last time I checked), expose the automation parameters to a sequence, which is routing its midi to a V-Rack. It only routes the midi.
So basically you can have in your chunk sequence, with the timeline, midi events which will be sent to the V-Rack. How you convert those midi events into controlling VePro faders is a separate question. VePro has its automation mapping facility which might be one way but I'm not sure if you can control the actual VePro mixer faders by using midi automation or not...and you would lose some resolution that way also since midi has a range of 0-127.
But as far as I can remember, DP does not expose plugin parameters from the V-Rack....to the chunk sequence timeline where they can be automated directly.
Hope that makes sense.