that would be ideal, but looking at ezasynchronouspublishing.js this won't be trivial as this JS code is written to used only one time in a page (hardcoded ids + *module pattern* designed for one content tracking...)

Maybe a simple and good enough solution would be to have a different message depending on whether it's an asynchronous publishing and in this case write a message explaining that the content will soon be published with a link to its future parent ?