Well, no, it does not make it clearer. However, it is peripheral to my point. Which is that it is unlikely that BU miners will creep up initially. They will likely go straight to 2MB. For as long as it takes to clear the transaction backlog. For such would deliver a demonstrably better user experience (faster cheaper transaction processing) relative to the other chain.
Yes, further increases may be likely to be more incremental in nature.
they would actually creep up in increments, thats the smart thing. (as the 500k berkely locks/levelbdb upgrade drama has taught the community)
they done so in the past.(policy.h v0.7 0.5mb, policy.h v0.8 0.75mb, now 0.999mb)
but here is where your missing a few idea's
moving at say 250byte a block increments, means they can reasonably safely get to 2mb in about a month.
so it wont be 2mb activation day .. and it wont be 2mb by 2020 by being slow about the increments.
250byte per block increments = 4 weeks-ish
500byte per block increments = 2 weeks-ish
1kb per block increments = a week-ish
they may even once say the first few blocks above 1mb havnt caused issues. increment it in 0.25mb increments. taking possibly a day or less to get to 2mb... but one thing is for sure they wont just jump to 2mb straight off. they will see if there are unknown bugs/orphan risks etc
so not that long when you think about it