The Control-M for Informatica module uses Web Services (WS) to communicate to the Informatica server. The module can be installed on top of Control-M/Agent anywhere on the network as long as the Informatica server host is accessible from that machine. You can configure the jobs to start a workflow from start, start from a session, recover and each control-m job has access to the Informatica workflow and session log so it gives the product to support a single point to monitor everything.
The biggest design consideration is how control-m bills. You pay per job. So it the traditional cmd line world you could have 300 workflows each calling a single session and the cron or other cmd line scheduler could just rip through calling them all in parallel or series at no cost. but control-m you need to look at bundling as many sessions into a workflow as you can or it can get pricy very quickly.
Also, control m lacks some dynamic-ability. Let's say you are running a workflow using through concurrent option so you can call that workflow multiple times to have multiple parallel instances running, at the cmd line you start the same workflow passing in a workflow run instance name/id. control m you have to have 2 jobs flows.
So depending on how complex your scheduling is going to get, sometimes using the cmd task in control -m does give you more flexibility and is better.
It all depends on what you are doing. Hope the insights help.