File to Proxy scenarios, varying Transport Protocol

I need to define a "normal" scenario which will pick up files from an external FTP location, and process them with a server proxy.

But there's the additional need to pick files from an arbitrary local file server in which some users could drop manually files they received by mail, which should be processed in the same way.

This forced me to define two communication channels, two sender agreements, etc, and dupplicate in general all the directory objects. The CCs vary in the protocol and directories properties, but the content conversion parameters are also dupplicated (Recordset, fieldNames, fieldSeparator and such).

I will have this same situation with at least 4 interfaces which leads to a lot of objects proliferation.

Is there any way to avoid this massive dupplication?

Many thanks!