I don't have any specific stats to link to, except the article you've already mentioned (which I read yesterday and found really interesting).
I don't think it matters which platform the app is on or how many settings there are, you should assume that most users won't change things (as the article mentions, developer tools may be the exception).
Either way, you should make your app the most welcoming and useful with the default settings. Taking it a step further, you should remove settings where it's possible to include the feature in place, contextually.
Some cases where I've noticed users don't change default settings:
Photoshop default colour management for RGB means image colours get changed when saving for web. It's possible to fix this, but a huge amount of users still complain that Photoshop does it. I think it was a poor choice by Adobe to use the default settings they have for RGB colour management (if anyone's interested, I've written an article on how to set things up so colours don't shift).
iOS settings being in the settings app, rather than the app itself. This seems to add an even bigger barrier for exploration and change to settings, because users often don't know the settings exist. I asked ten developers about their experience with using the iOS Settings app for settings: http://bjango.com/articles/settingsapp/
I think a good set of general rules for settings is:
- Where possible, remove settings and have the feature in place, where it's likely to be discovered and where it fits contextually.
- If you need settings, like account set up, have them as part of the welcome process for your app or as part of coaching while the app is being used. Then also make it possible to edit and change the settings at a later date.
- If you must have settings that aren't a natural fit for in-place or as part of a welcome set up, assume most users will never see them.
Setting good defaults is critical.