The only difference is that without staying at the 1 MB blocksize limit, we wouldn't be able to force people to use SegWit. Even Coinbase claims that they will have 100% SegWit support by the middle of the next week. Increase of the blocksize will be mandatory in the future after Lightning Network becomes used by thousands of people. If we didn't go for SegWit, I guess we would be constantly raising the blocksize which would lead us to nothing. [...]
Exactly. A blocksize increase should be seen as a last resort and only when all other options have been exhausted. Seeing how the mempool is currently close to empty while SegWit still only accounts for roughly 14% of transactions I'd say we still have some leeway, especially once Lightning Network becomes more widely adapted.
We now have a solid foundation for future scaling solutions. If Core had simply increased blocksize right away, SegWit and thus Lightning Network deployment would have been postponed with each subsequent inevitable blocksize increase. Businesses tend to externalize costs to the community wherever possible. Pollution in the case of industry, blockchain bloat in the case of crypto. Case in point: Coinbase not caring about batching transactions until just recently. Why should they? Blockchain space costs nothing to them, while implementing SegWit does. That is, unless they get flak by the community. And unless blockchain space gets accepted as the scarce resource that it is. So finally, here we are.