Umm, wrong on a few acounts:
Having both drives on the same channel is bad to begin with, here's why:
They dont share the bandwidth "So each HDD gets 50MB/s" that is wrong. Its worked on a master/slave system. That means only one drive can access the 32 bit path at one time. The master has precedence. But when the master drive recieves a special signal, it then replies back a signal to notify the slave drive that it can use the IDE cable.
So transfering data from one drive to another on the same IDE channel works like so: CPU receives command to transfer data from drive A to drive B. CPU issues commnd to PCI. PCI issues command to IDE bus to HDD A to write data segment to main system mem. HDD A receives command and verifies that command was issued to HDD A and not B (master/slave verification). HDD A reads platter for data and stores into buffer. Buffer contents are then sent to system mem through PCI bus. PCI bus signals CPU operation completed. CPU then issues command to PCI bus to write data to HDD B. PCI bus signals HDD B to receive data from system mem. HDD A receives the command, determines command is for HDD B, sends signal to HDD B. HDD B receives signal and responds readiness to receive data. PCI bus activates transfer of data from system mem to IDE channel. HDD B writes data physically to platter.
ATA IDE channel consists of (80 pin connector) 32 lines for transmitting data. 32 lines for addressing data. The rest are for signals to read, write, HDD boot detection, burst transfer verification, ready signals, etc etc. The address lines and the data lines are connected to both HDD sharing the channel. 1 or 2 lines are used to determine which HDD will control the channel at one time. So only one HDD can access these lines at one time.
The biggest determining factors for speed of HDDs has to do with seektime (its in ms, while transfer rates are microseconds), RPM, and disk density. SCSI drives perform better because of RPM, and seektime. Also, they perform better due to drive motor quality. Hence why they are more expensive and less in demand.
You could gain a marginal, and probably unmeasurable in realtime, difference if you transfered the data by having each HDD have its own IDE channel. This would release the need to verify master/slave conditions. But its a drop in the ocean. Burst rate is a moot point also. So what if the buffer can burst the data on the PCI channel directly to memory if it takes the same amount of time to fill the buffer? Its like filling a bucket with water. You can fill it faster if you fill up a balloon first, then pop the baloon over the bucket. But it takes the same amount of time to fill the baloon beforehand. Burst transfer works best when look-ahead reading is used and the data is sequential and small enough to be less than the buffer size. It doesnt mean alot when the filesize you are transferring is 100's of MB large. Also, transfering small files means the HDD has to find each file and wastes time because of the seektime rating. Each file will take (for IDE) 9 ms to find.
Whats 9ms to transfer speed? ATA133 means transfering 133MB/s. The PCI bus is 33MHz and 32 bit. 33 million cycles x 32 bits divided by 8bits/byte = 133MB/s. Or 133 kb/ms. 9 ms is wasted trying to find a 64kB file that can transfer in 0.5ms (IDE ATA bursted).
SATA is gonna be a joke. At least for single drives. It wont have much in the way of better tech for the platters, motor, and magnetic head. Its all about the interface. It will have a higher capacity to transfer data by using a serial signal instead of a parralel signal. But the true limitations of a HDD that can be seen by the naked human eye will not be improved. Realworld operations will hardly be increased. They will be increased, the interface will have more headroom for inovation, but the increase will likely be about 10%. Considering the average transfer rate for your everyday IDE HDD is around 45MB/s in good conditions, getting to 50MB/s doesnt really impress me. The true limitations need to be addressed more than the interface.