prismweb dude, we figured it out lol... You don't have to assign email role to customers, just assign the role to the server. I'm the same way, I don't mix hosting and email (I have a separate dedicated email node just for email). The fix Adam figured out for me is acceptable and simple, just enable the Email role to any hosting server, you can then mark the Email role on that server as "disable placement" so no sites will be able to even use the role or be assigned it. It's just required to be assigned to the server so the server can send phpmail... I don't know if you need to do the "restart php container" on every site you add to that server, it might just be needed for any sites "that's added AFTER the email role is enabled for the server". I think once you enable the email role on the server (then disable placement) then any new sites you add to that server will have the phpmail capability available without having to restart the php container.
I'm in similar boat about waiting to migrate a fleet of cPanel's. Except for me I'm more interested in some other features coming down that I need to be really comfortable with it, like next months Roadmap items to have a second control panel available in case the primary dies. I want the Apache config capability as well, because I'm not sure how well Enhance can handle some of my bigger sites getting millions of pageviews per day, pretty sure Apache will need to be tweaked for that. It's not absolutely needed, but I'd be more comfortable with some ability to see resource consumption on accounts as well, since the current availability is really poor, if a site is going ape on the database and killing CPU, it will be hard to track down which account is responsible. That's dangerous situation for mass hosting.