Maybe tweak that "corrections" algorithm then. For example, if 5 competitors put Subway at the corner of Main & Elm but Apple Maps has it 3 blocks away, adjust it to about 90% (in favor of the 5). While that wouldn't be as accurate, it would be much closer than "as is".
Furthermore, add a group "verify" mode to the app. Instead of dropping a red pin, drop a yellow one or maybe have a question mark next to it as a call to Maps users in the area to verify the location when they actually go there. Get X number of verifications that it is on Main & Elm and adjust the official entry to Main & Elm (maybe still in verify mode to gather another X number of votes).
OR, adopt a hotels.com/trivago/progressive, etc strategy of showing where Apple Maps thinks something is AND where some of the other guys think it is. Then "know" when the user spends some time at one of the points and ask them "was it there" (where "there" is where they spent the time).
And/Or, when in doubt or when enough users identify a wrong pin, adopt an approximate flag (maybe some kind of graphic bar) that shows where Apple Maps thinks it is to where other Maps pin it with user input too. Back to the Subway example: instead of showing a (wrong location) pin at a specific point 3 blocks away, this might show a zone bar from that pin across the 3 blocks. These bars could then be the call for users to narrow the search when they go to the actual location. With X number of "this is the actual location" verifications from users, reduce the bar length or zone. With a few more verifications, switch to a pin.