BU is user requested scaling.. its not like it actually will contain 16mb of data tomorrow.. miners have their own preferences and will grow incrementally.
EG bitcoin is only 1mb.. even in 2016 you yourself bleeted that blocks were generally not yet at 1mb and there was still room for growth
EG bitcoin is only 1mb.. even in 2013 you yourself know blocks were only 500k full
meaning even with 1mb rule blocks were not 1mb..

so a 16mb, 8mb, 2mb rule does not immediately make every block that size. its just a BUFFER..
EG you can have 64gb of ram but never be at full memory usage
EG you can have 3tb hard drive but never fill it.. but atleast relax you have more room then you need for the future

but speeking of the future.. lets look to the past
guess your too young to remember 16 years ago when hard drives were a max of ~4gb and most users though that 1.4mb of reusable transportable data was great and more than we needed

also you mention sigops.. werent you the one crying that transaction bloat was straining bitcoin due to so many sigops.(u know the 11minute validation time doomsday you bleeted out like a sheep)

so tell me.. what REAL WORLD scenario can you see that a user needs to use XXXXX sigops in one go.
so tell me.. what REAL WORLD scenario can you see that a user needs to use XXXXX sigops in one go instead of batches
so tell me.. what REAL WORLD scenario can you tell me would be a reasonable sigop limit.

EG using sigop rules to limit spam instead of expensive fee wars is actually good for bitcoin and good for users.

for future reference:
remember the hypocrisy of you also favouring a system of discounted transaction costs via segwit and no sigops, which will result in more spam when you cry about spam in the future..

edit:
wait i see the plan now that you hope validation times are no issue you are happy for spammers to spam to cause a fee war.. hmm i wonder why. hmm..
anyway i digressed. so back to what i really want to know from you..

so tell me.. what REAL WORLD scenario can you see that a user needs to use XXXXX sigops in one go.
more precisely.. what REAL WORLD scenario can you see that a user needs to use XXXXX sigops in one go instead of batches(separate tx's)
so tell me.. what REAL WORLD scenario can you tell me would be a reasonable sigop limit.