Stop with the "Random Guy", you're fooling no one with your stealth re-edits.
Installing CU .493 on a base .1 image will generally create an ISO equivalent to .493 applied to .194. If that's true, why don't users begin with .1?
Two reasons:
1. MS doesn't test every possible update combination, they only guarantee applying CU to RTM works. If there's a patching bug, then no one can figure this one out since they're using RTM and you're the outlier on .1. Then it's your burden to convince it's not caused by .1.
2. Everyone has suggested you build an integrated image, THEN remove components. Even though NTLite tries its best, some combinations of updates and removals in the same pass can create broken builds. The processing order is critical to success, especially when it applies to features CU is updating.
The problem is you cannot predict what MS will include in the next CU. A preset which worked before can suddenly be broken by a later CU.
Separating removals in a second pass lessens that risk.
Final note: what's the size of .1 updated to .493 vs RTM updated to .493. How much disk space is saved?
Do this challenge and come back with actual results, if you want your arguments to be convincing.