That's how we use it in ShockWallet, but it makes NWC redundant, the lightning address bridge server uses it to get the invoice from the node
Example implemented here:
GitHub.com/shocknet/bridgelet
Is this something that could be used to allow nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm Hub wallets to have custom lightning addresses that fetch invoices using something like #NostrWalletConnect?
https://github.com/nostr-protocol/nips/pull/1460
#AskNostr nostr:npub1xvtwx6tduaxnn9v3y7uasskl277achgu0tu2qncmc7hdsz6y2zyqce64sa
Discussion
I ask because the only thing Alby Hub provides for an isolated wallet is n order to differentiate it from your full lightning balance on the node is a separate NWC connection string.
I believe that's a limitation of their node software not nwc itself, we so things differently with lightning.pub so each user wallet can have there own or multiple nip69 offers/lightning addresses