I've just done some further testing to try and establish what is and is not expected to work. I have ruled out modifying the post expiration time after the form is submitted, that makes no difference.
I included all of the %%placeholder%% fields in the email to confirm which work with a post expiration notification.
The placeholders for the current post work (e.g. %%POST_ID%%, %%POST_TITLE%% etc.).
Views shortcodes do not work unless the id attribute is used with the %%POST_ID%% placeholder, e.g. wpv-post-title id="%%POST_ID%%".
Because of this the id attribute cannot be used to specify the parent post id, and so it is only possible to output fields of the expiring post itself.
There are two placeholder fields to display info from the parent post (%%POST_PARENT_TITLE%% and %%POST_PARENT_LINK%%), but... they don't work. I'm reporting that as a bug.
Regarding your last update, I would expect the title to display, but each of your types fields, are they fields of the post that is expiring (in which case they should be output when using the id="%%POST_ID%%" attribute)? Or are they fields of the parent post (in which case they are inaccessible to notifications, regardless of the above-mentioned bug)?
For this latter point—that fields from parent posts cannot be included in notifications—I've created a feature request.
Ahhh, bummer, yes the fields I'm trying to send are from the parent post. I suppose if we can get %%POST_PARENT_TITLE%% and %%POST_PARENT_LINK%% to work I could live with that. Any idea when that bug might get fixed?
To your question about the emails, they are not totally blank, they contain the plain text I enter and this field [wpv-post-link id="%%POST_ID%%"] form the child post.
Maybe there's a workaround here? Could I possibly pass some parent post fields to the child post upon submission(using generic fields?), so then those fields would be available for the notification email?
I only reported it this morning and quite a few people are away this week, so it won't get any attention before the new year, and as to how long it takes to resolve I can't say because it depends on what code is affected.
Generic fields as a work-around might be possible.
It would only work if you save the generic fields, i.e. use "persist": 1 in the options so that the field values get saved to the database.