You think it'll be possible to couple two thunderbolt 1 ports to form a bigger pipe so to speak? I know thunderbolt 2 is just thunderbolt 1 coupled
Thunderbolt 2 is
not Thunderbolt 1 coupled the way Ethernet ports are bonded. Thunderbolt 2 is the same Thunderbolt v1 bandwidth just allocated a different way. The channels are physically just as coupled in the wire in v1 as v2. The only thing changing is the logical overlay , better data management controls, and some small behind-the-scenes protocol adjustment. (along with matching the evolution of DisplayPort to v1.2) The external facing physical ports are exactly the same as there were.
Trying to bond two physical TB ports that are provided by the same Thunderbolt controller doesn't buy you anything. Both physical ports share the same "back end" so "bonded"/"coupled" together isn't going to make throughput to the underlying host system go any faster.
Bonding two ports that are each provided by a separate TB controller doesn't really help all that much because because destroying the opaqueness of the PCIe data mapping. Could huff-and-puff to offset the complexity by adding another layer on top but for cases like "storage throughput" it is far simpler just to use the "virutal bonding" mechanisms that already exist at a higher level and just overlay them onto the independent ports ( RAID 0 of storage on port A1 and on port B1 ).
but I'm imaging say hooking an external GPU up and instead of daisy chaining it plugging in two thunderbolt 1 cables into both ports (if it has two) for 20Gbps one way and another 20Gbps another which would exceed even TB2.
How many GPU cards have you seen that plug into two PCIe slots? Exact same impediment issues. Data arrival sync issues because of the independent two paths. Gross mismatch with how the PCIe controller is mapping things out at the lower level. etc.
Rube Goldberg solutions trying to make GPUs work aren't going to be effective because Thunderbolt wasn't primarily designed for that.
Honestly it seams like TB1 could be converted to TB2
It is the exact same set of wires. Essentially that all TBv2 is.
and I think Intel and Apple gouged allot of loyal paying customers by not just releasing TB1 with the 20Gbps option like TB2.
Not segregating the data is actually harder to do with mixed data workloads. If not implemented correctly folks would be gouged a whole lot more. Just doing the logical remapping requires a more complicated controller be built. More complicated , more likely have bugs. Hardware with bugs is just broken. ( there are no 'patches' can distribute ).
Similarly it is cheaper to implement larger logic designs on newer, smaller fab processes. Even if Intel threw manpower at earler design and got out all the bugs it would have cost even more to implement TBv2 on 1-2 year old processes that TB1 went out on.
It is far better just to implement something simpler and then incrementally move to more complex solutions.
The whole thing is just weird to me.
It is normal. USB 1.0 was followed by USB 2.0 which was followed by USB3.0. The gaps are 4-8 years long, but same general technology progression. It is just a slightly different mechanism for doing the progression ( not necessary primarily just clocking the signals on the wire faster. Like much of 1.0 -> 2.0 ).