Maybe, but its not really a nostr issue.
Its not a lightning or LUD issue either.
Its a provider feature for their custodial accounts. NIPs are best as bare minimum specs for building blocks, vs documenting implementation specific options.

As an example, I wouldnt want NIP96 for file servers to standardize and force those kinds of providers to implement transforms for downscaling, text parsing, transcript producing either. Those features are nice to have, but not essential for core function. The more bloat to a NIP, the more moat building it creates for incumbents

What may be appropriate would be a NIP standard for discovering client/relay/services, and their feature sets. Individual domains would need to self regulate though, so it may just be passing the buck on the issue