I am truly unsettled; I have switched from Core 0.11 to Classic 0.11 to Core 0.12 to Classic 0.12 and it is totally possible/likely I will switch again. Perhaps I will try using more advanced mathematics, above and beyond high school maths.
#0: Reducing unproductive contention in the Bitcoin community is a personal goal.
#1: Right now my top interest is in the vulnerability to transactions with lots of inputs that lead to long compute times for verifications. One wonders why we don't see bad actors using this against Bitcoin relentlessly. Maybe there are less malicious folks attacking than I hear about? Maybe the bad guys don't know how much this can hurt?
#2: Secondarily I would like to see a concerted effort be made to 1) educate users about setting fees well to facilitate quick confirmations, i.e. to avoid long/painful/anxiety-causing commit times and 2) enhancing wallets to make it automatic and default to have high enough fees.
#3: Thirdly; I do highly prefer adoption much more than increasing fees which means to me capacity. Increasing fees will have to come eventually but in the meantime I would happily sacrifice fees until adoption is really widespread.
#4: Fourthly; Is there something to the Bitcoin Unlimited stuff?
#5: Lastly; all of those other features/functions like transaction malleability, etc. Perhaps these should be higher on my list but I haven't dug into them yet; sorry.
With those in mind;
block size limit, e.g. 2MB; helps with #3, hurts #1, we should resist doing it just because it seems obvious, obvious is not a reliable attribute
SegWit; helps with #3, hurts #1, introduces other complexities that might have subtle consequences
limit inputs: all by itself this is great for #1, seems simple enough, workaround is trivial, i.e. create multiple small transactions
#0 this can be solved by core adding in the code, to not cause the contention they cry about. then with all the different code bases (btcd, bitcoinj, classic, core, etc) having the code, it is then just a waiting game to see if miners decide to upgrade too knowing all the users are ready to accept such changes.
#1 this can be solved by knowing REALISTICALLY the times it actually takes to sort through a transaction with 50 inputs, 100 inputs, 1000 inputs. and then see how many times people have made a genuine(not attack) transaction of such. to set an arbitrary rule to ignore transactions with such amount of inputs, just like they ignore transactions with no fee.
#2 1) also educate people how to code/make transactions with least bloat/random use of inputs. to help them decrease their own cost of sending a tx, aswell as helping reduce chances of verification time problems.
#2 2) its a little too early to push the transaction fee up.. id say it should be a slow process over years-decades, not a rush job to try making 3000+ transactions every 10 minutes have high fee's meaning the fee naturally increases because there are only 2000 transactions(average) allowed in per block.
imagine it. 3000 tx pay 4c.. 2000 get allowed in block1 and 1000 in block2.. then the next 3000 tx only 1000 is in block 2 and 2000 are in block 3. meaning that if the 3rd set of transactions have any hope of getting in block 4 or 5 they are likely to have to pay a premium to fight off competition..
so within 5 blocks the price begins to rise.
the fee is not an essential part of mining income. it is just a small bonus. it does not need to, nor should offset the reward for many years. because the reward is part of the mechanism that helps the speculation of the deflationary price(price rise). by flooding miners with lots of coins will make them spend them just as fast which not only affects the valuation of bitcoin. but also pushes miners to add more ASICS, and raising the difficulty. making bitcoin more centralized due to the smaller pools losing the competition. also pushing customers/users away from bitcoin because a fee does not actually guarantee the very next block(no guarantee of confirmation in 10 minutes)
pushing the fee has a knock on affect on many aspects. and there is no logic to push it too fast.
#3 agreed. allowing twice as much buffer room(2mb) to grow, or even 4x as much buffer room(2mb+segwit) allows for NATURAL SLOW growth without pushing or irritations and without demanding to dev-team for just an extra spoon of buffer every couple months knowing it takes 2 years to get the spoon.
#4 i personally am not in BU camp, xt camp, classic camp or core camp. i just want more buffer space without beeding to be spoonfed by developers. BU is the premiss that there needs no hard limit. and miners can set their own preferential soft limits. but best to ask someone(hopefully they reply unbiasedly) who has researched it in more detail
#5 i agree it doesnt need to be a classic OR core. it needs both. in combination
edit
your final sentence answered the #1 for yourself and more elegantly then i did