Can an ExtensionFoundation-based extension on macOS have its own extension point and host its own extensions?

It is possible for an extension to an app (based on ExtensionFoundation) to declare its own extension point and host its own ExtensionFoundation extensions?

Based on the documentation, I am guessing the answer is no, but worth double-checking.

What would be the reason to prevent this? Every ExtensionFoundation extension runs in its own process, and may have need to be extended safely just as its host app does.

Thank you!

Can an ExtensionFoundation-based extension on macOS have its own extension point and host its own extensions?
 
 
Q