I don't think you could achieve that. V2 tasks are run without locks by design, since they are intended for non-critical and statistical updates.
https://help.sap.com/saphelp_nw70ehp1/helpdata/en/e5/de86e135cd11d3acb00000e83539c3/content.htm
Processing the V1 modules involves transferring the contents of the update tables VBMOD and VBDATA to the application tables of the database. The changes are not actually made to the tables in the database until the database LUW in which this takes place is completed. The SAP locks are released and, if V2 update modules exist, the V2 update is started. This is similar to the V1 update with the exception that there are no locks that have to released and no search for a process for further processing.