Answer
One workaround is to expose COMMAND_SYS.Mail as a custom bound action through Projection Configuration on any commonly-used projection, then call that exposed action from a Projection Task inside your workflow, passing in the from, to, subject, and message body as parameters. This effectively gives a workflow direct access to the standard mail-sending API without needing an Event Action or Report Rule as an intermediary.