This is the type of thing that you should absolutely be reporting to support, rather than posting in the forum. You need to get your question in front of the right people to act on ithttps://support.market.envato.com/hc/en-us/requests/new?ticket_form_id=10590
I also vote for placing Font Awesome in your theme/plugin and properly enqueueing it.
Using a CDN for Google Web fonts is one thing – if they don’t load, you have a system fallback.
If Font Awesome icons don’t load, you’ll get a bunch of unknown characters since they’re not in the standard unicode set.
Sidenote: loading jQuery from a CDN is your choice if you’re managing your own site (though then you have to manually keep it up to date), but if you are releasing a theme or plugin publicly you should NEVER do that – it would be very irresponsible (and also isn’t allowed by ThemeForest)
Using pre_get_posts isn’t an issue, but you’re not allowed to adjust the posts_per_page that way because there is already a core WordPress setting to do that (Reading > Blog pages show at most). So your code will override the standard functionality, and that’s why it’s not allowed.
Not the main point right now, of course, but down the road it’d be great to have a status.envato.com which would list the current status of the marketplaces, other Envato properties, the API, etc. Any currently known issues being investigated would be listed there.
We all understand that hiccups happen from time to time, but being able to quickly determine if the issue is known already will save users a lot of strife, and prevent Envato Support from being flooded with duplicate tickets once they’re already aware of the problem
It would be super simple like http://status.twitter.com/ , but this type of thing would be greatly appreciated