Allow uncategorized entities to be added to channel structure (without actually being added to a node)

Who would benefit?

When customers have product categories that are not categorized, but still need to expose them in downstream systems, or if the customer does not have a hierarchy approach at all...

What impact would it make?

No need for dirty walkarounds where dummy channel nodes (CN001,CN002,CN003 etc etc) are created with 2000 products in each, just to have a way to get the entities out. This approach (which unfortunately is quite common) require a non-userfriendly hierarchy and most often use link rules to add the product to the right bucket node.
This approach also leads to performance degredation and unwanted events fired when nodes are filled and emptied with links.

Another common approach is where entity listeners are used to get data out, which should require a scheduled extension to export the queue (but unfortunately, too often the data is sent out in the listener.... ). This leads to a delay when exporting data, as we need to wait for the scheduled extension to kick off.

How should it work?

Allow entities to be added to a channel structure for any given channel (UI, REST, Remoting). The backend needs to add the entity to the channel structure table, and any event related to this add will generate a channel listener event (and other activities).

There must be a new database table to host entityid and channelid for all uncategorized products, so that they are added again when a channel structure is rebuilt.

An uncategorized entity which previously was assigned to a channel strucutre, and then included in a channel node (becoming categorized), should need to be removed from the uncategorized table, to avoid products being uncategorized and categorized at the same time...

Why is it needed?

No current system friendly approach to get unstructured data out through a channel.