Hello Bjorn,
if I get you right, the after loading shall trigger the second transaction in that proposal. This would be some kind of lazy execution of the second transaction. An alternative would be to trigger the second transaction out of an AFTER_SUCCESSFUL_SAVE determination. Those determinations are immediately invoked after the BOPF's save phase (here the save phase of transaction 1) is successfully done.
Best regards
Tilmann