Data Pump dumps as normal, but instead of an email to you, it calls a batch script in the post process code. In the batch script, it calls your database with the command line to execute a macro in the database. The macro that you will need to set up in Access will turn off warnings, then generate the reports (execute the code behind the button you push), and finaly exit Access.
Another Data Pump process gathers the reports by monitoring for them and dumps them to Excel. Again, in the post process, call a batch script which calls your Excel macro.
email can be done by VBA if you would prefer, but it is probably easier to have the export of the second Data Pump job send out a link to the report or attach it. The email happens after the post export, so your macro changes should be finished before the email is sent out.
I'm just wondering why you need Access to do anything? Monarch can open up to 10 Access tables/queries at once using external lookups, then the reports could be set up to run as summary exports from Monarch. Then the whole process could remain within DataPump without the need for scripting?