Applying On-Prem EAP with New-Remote Mailbox

BACKGROUND: my org is in a hybrid AD/Exchange environment, and will remain so for some time.

All mailboxes, other than a very small number with on-prem dependencies, were migrated to M365 a few years ago; we will continue to have 1-2 Exchange Servers on-premises for both management and some legacy on-prem processes.

All user accounts are created on-premises, and synchronized to M365 through Entra Connect Sync.

Our on-prem EAP has the exact address syntaxes that we need [applies to "Users with Exchange mailboxes" + "Resource mailboxes" + "Mail-enabled groups"].

I haven't found a clear answer to the question: with an Exchange 2019 (and soon SE) server on-premises - with users initially created on-premises - is there a way to provision new EXO mailboxes [using the 'new-remotemailbox' cmdlet], such that the on-prem EAP applies during creation?

I've been working with these two references, but so far haven't found a way to make the "new-remotemailbox..." cmdlet work to (a) create a new account on-premises and (b) ultimately have an EXO mailbox provisioned with the on-prem EAP addresses in place:

On provisioning mailboxes in Exchange Online when in Hybrid | Microsoft Community Hub

https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/new-remotemailbox?view=exchange-ps

Any thoughts or suggestions would be welcomed! (OR - perhaps it just can't be done?)