Design != production. I never said Apple produces the hardware. You can design software to specific hardware specifications without physically producing the device. The closer you can get to the hardware when designing software, the better software you can *potentially* design. Having to have a one size fits all OS that covers all bases is anything but helpful.
Samsung does this better than anyone including Apple, so your point is invalid & moot because none of what you wrote above has do with or is why the iPhones better short/long term overall performance (in some cases) or exceptional benchmark test results which in certain instances favor the iPhone over it's high end Android competitors.
Unless you're thinking of phones from 4-5 years ago, carrier bloatware has little to nothing to do with the performance difference between Android devices and iPhones. You'd have to go into the operating system level of how Apple handles everything from user touches to multitasking to get a full understanding of how very different the software design philosophies are for both products. If the bloat was the determining factor, there would be no reason previous generation iPhones could keep up with the top of the line Android phones with half (or a third) of the RAM and weaker GPUs and experience less of the slowdown after the honeymoon phase is over like Android devices tend to. The code itself has a lot to do with it. Not saying one is better than the other at all (because they have completely different use cases), but the difference in paradigms definitely plays into the efficiency of the OS.
Reading comprehension is a must because you conveniently skipped over that I already plainly stated iPhones ALSO perform better with less powerful hardware due to the fact Apple doesn't utilize Java for it's apps & the iPhone has a NAND drive which provides the iPhone with much quicker read & write speeds. Furthermore Apple uses LCD screens vs OLED like most high end Android branded phones, so iPhones use less of the overall processor power & maintain better battery life. However to deny the lack of additional carrier software on IPhones doesn't allow them to run much smoother with less lag vs top spec Android models riddled with extra, unnecessary bloatware shows your lack of knowledge of how an OS file system works in conjunction with applications & the phones hardware.
Reread my quote homie. You're getting into straw man territory based on your assumptions of what I said. Even in my post you quoted I noted that the issues are incurred if you install custom ROMs instead of simply using a rooted stock ROM with said bloatware removed. Furthermore, most of your other performance notes are based on an assumption that all bloatware you remove gives you all of those benefits. A lot of the bloatware (duplicate internet browsers, health apps, etc.) won't give you much if any performance increase over simply disabling the app itself. The real benefit is the storage space gained. The reason I even brought up roaming is because once you remove carrier bloat and free up space, you can get even more performance (including speed and battery life) with some of the better ROMs/custom kernels out there.
More garbage rants with little knowledge of how an OS runs. Disabling the app doesn't prevent some apps from running again in the background (as all your doing in some cases is just putting many of the disabled apps in a temp sleep mode) or starting up again once the phone is rebooted, nor does disabling apps delete them completely off the file system.
Additionally, the real benefit isn't just the storage space gained from eradicating the apps from the OS, as the more free space you have in your phone's internal memory, the faster your phone also can write to the disk. Thus your premise that removing a lot of the bloatware "won't give much if any performance increase over simply disabling the app itself" is absolutely FALSE & INACCURATE.
The bolded is completely incorrect. Android as the masses know it is Google Android not AOSP (Android Open Source Platform) Android. It's NOT the open source version of Android.

Again, INCORRECT!
"A stock ROM is the ROM that comes with a device; the device is "stocked" with that ROM by the manufacturer. Android is generally customized by the manufacturer to some degree; at minimum there needs to be device-specific drivers and so on for Android to work on a particular device. As Flow notes, customizations may include a custom theme, launcher, and default apps like HTC Sense does.
An AOSP ROM is a ROM based on the Android Open Source Project. In the purest sense, AOSP refers to unmodified ROMs or code from Google. The name is often co-opted for custom ROMs that are very close to the original AOSP, since these ROMs still need to be customized; for example, I can't download/compile the Android source code and run it on my Samsung Vibrant without doing a whole lot of customizations. The name is often abused to refer to ROMs that don't have a custom launcher or many of the other modifications carriers make with Sense, TouchWiz, Motoblur et al., although they may still be themed. A more accurate name for plain, mostly-unaltered ROMs for non-Google devices is probably "vanilla ROMs".
Techncially, stock ROMs are all AOSP ROMs apart from the versions of Android that haven't been released yet.
To further add to the confusion, a "custom ROM" does not refer to customized ROMs in general. That term specifically refers to ROMs that have been customized by third parties (i.e., not the manufacturers or carriers). For example, I'm running a custom ROM that is just a re-themed and tweaked stock ROM. CyanogenMod is another example, and it has many features built from the ground up rather than mere tweaks. Most AOSP ROMs you'll find for a specific device are stock ROMs that have been customized to remove some of the manufacturer/carrier tweaks and make them closer to the pure AOSP experience."
What's the difference between an AOSP ROM and a stock ROM?
"Generally, most people use the term stock ROM to mean the manufacturer's ROM that came with their device (possibly including any OTA updates). As t0mm13b points out, this ROM almost certainly wasn't built from AOSP: the source will be based on AOSP (or Google's internal sources, if the manufacturer is big enough to have access to them), but it will include any drivers for that device, as well as the manufacturer's customizations such as Samsung's TouchWiz or HTC's Sense"
What is the difference between AOSP and AOKP?
Android A to Z: What is the AOSP?
"AOSP is a term you'll see used a lot -- here, as well as at other Android-centric sites on the Internet. I'll admit I'm guilty of using it and just expecting everyone to know what I'm talking about, and I shouldn't. To rectify that, at least a little bit, I'll try to explain what the AOSP is now so we're all on the same page.
For some of us -- the nerdly types who build software -- the full name tells us what we need to know. AOSP stands for
Android
Open
Source
Project. The AOSP was designed and written by folks who had a vision that the world needed an open-source platform that exists for developers to easily build mobile applications. It wasn't designed to beat any other platform in market share, or to fight for user freedom from tyrannical CEOs -- it exists as a delivery mechanism for mobile apps -- like
Google's mobile apps, or any of the 400,000+ in the Google Play store. Luckily, Google realized that using open-source software would ensure that this operating system/mobile application content delivery system is available for all, for free. And by
choosing the licensing they did, it's also attractive to device manufacturers who can use it as a base to build their own mobile OS.
The premise plays out rather nicely. Google writes and maintains a tree of all the Android source code -- the AOSP. It's made available for everyone (you, me, manufacturers you've never heard of and not just big players like Samsung or HTC) to download, modify, and take ownership of. This means the folks at CyanogenMod can add cool stuff like audio profiles. It also means folks like HTC can change multitasking in ways that many of us don't like. You can't have one without having the other. The big players then use their modified version of this source to build their own operating system. Some, like Amazon, radically changed everything without a care to use Google's official applications and keep their device in compliance with Android guidelines. Some, like HTC radically changed everything yet followed the Android Compatibility Program (ACP) so they could include Google's core application suite -- including the Google Play store. Some, like the folks at CyanogenMod, enhance the pure AOSP code with additions but don't change the overall look and feel. Again -- that's how this open-source thing works. You can't have it without allowing folks to change it as they see fit, for better or worse."
Android A to Z: What is the AOSP?
I do agree that it wouldn't hurt to have Samsung at the forefront, but unless they petition for ALL manufacturers (which makes no sense from a competitive standpoint), you still have LG, Asus, HTC, and a gang of other Android phone manufacturers that will have to do the same thing. There's no incentive in Samsung making such a move when they still customize Android, delay updates and add additional unnecessary apps to their devices. They'd have to change their operating procedures internally before doing anything. If Google mandates it, it covers all manufacturers who use Google Android.
Incorrect! Outside of specific Google Nexus phones, Google can't force the carriers to do anything in regards to bloatware because the carrier bloatware is installed on the final end product by the carrier itself & not the smartphone manufacturers. And Samsung's own proprietary apps or specific software programs have nothing to do with the original topic, as we aren't discussing customization on the manufacturers level, just the additional bloatware added from carriers.
Furthermore, for future reference, if you're going to have a debate about the inner workings of smart phones & the industry itself, I would suggest at least having a full understanding & factual information of what it is you're discussing. Sadly, most of this long winded, incoherent, gobbledy gook you wrote makes absolutely no sense or is completely flawed from a technical standpoint.