The argument is akin to saying "your program slowdown is - and I'm making up a number out of thin air - 50% caused by systems outside of your control so you should definitely spend 50% less time optimizing the things you can optimize".
The logical flaws are blatant: the % is an invention, and the truth or otherwise of the premise has no bearing on the action you can and should take.
If humans caused 100% of the change then we can stop causing it. If humans caused 0% of the change then we can't stop causing it and must adapt to it. If humans caused 50% of the change, then we can stop some of it but will have to adapt to the rest.
Obviously the premise has a huge bearing on the action we can and should take.
But since I'm forced to attack the strawman: let me put it another way: if humans are responsible for less warming than 100%, then we're going to have to do more to mitigate our effects, because we have to mitigate more human behaviour for the same outcome.
Until we're making meaningful changes - yet to happen - it's utterly irrelevant if we've caused 50%, or 100%.
Yes. Of course I am. We make those sorts of bets constantly, because Pascal's Wager doesn't work. We can't not make those sorts of bets.
When somebody says "the end of the world is nigh!" it is almost always worth waiting a bit to see if in fact the thing they're worrying about is actually a problem. Hindcasting is nice and all but the real test is: Does the warming trend actually continue as predicted and if so, once it does get warmer, do we actually see negative effects from it that significantly outweigh all the likely positive effects of warming?
[0] http://www.theguardian.com/sustainable-business/extreme-weat...
[1] http://www.foxbusiness.com/industries/2014/02/14/allianz-sto...
[2] http://www.theglobeandmail.com/partners/advinsurancetrends11...
[3]
http://www.climatecentral.org/news/what-happened-to-the-2013...
(Regardless, even if there were measurable negative effects you would need to balance them against the measurable positive effects to determine if the NET externality was positive or negative. It's silly to add up just one side - even the IPCC doesn't do that.)
Think of it from a programming perspective. You've suddenly discovered that your program runtime wasn't near as slow as you thought. Plus you've shown that most of the runtime is driven by systems external to your code. It makes sense to reconsider how much effort to invest in for code optimization.