parse-server: Latest changes breaking rest api and core views on parse.com due to addition of _PushStatus in _SCHEMA

Background: We are slowly migrating over to parse-server from parse.com. Current implementation is mongoDB migrated to mLab with both parse-server and parse.com running on the same mLab DB instance. We need to be able to run both in parallel.

Issue: Recent code changes in parse-server is causing issues with parse.com, particularly with pushes through rest api and even trying to view core collections on parse.com dashboard. The following error message is thrown:

{"code":103,"error":"Invalid classname: _PushStatus, classnames can only have alphanumeric characters and _, and must start with an alpha character "}

Cause: This occurred after updating parse-server with latest commits and then sending a push notification through parse-server. From what I found, parse-server is adding the following entry to the _SCHEMA collection:

{
    "_id": "_PushStatus",
    ...
    "failedPerType": "object"
}

While this works fine for parse-server, this is causing parse.com to completely break. Removing _PushStatus entry from _SCHEMA fixes this and parse.com dashboard and API works.