Sort:  

The cross-post is pretty much just an empty post with a link to the original but frontends view it as the original, @peakd started it and hive.blog embedded it as well and potentially others. That empty post has rewards declined but it still creates a post in the other community so if you have autovoters they can't differentiate if it's a real post or a cross-post so they're going to blindly vote on it and have all their returns declined, hence sending them to the DHF or null instead would fix the issue of autovoters not getting punished when an established author wants to use the cross-post feature.

So no rewards go to the original if the cross post is voted on?

Yes, peakd shows the original posts' upvote button on the cross-post as well as the full preview of the original post when you open the cross-post, but on the blockchain level the post itself is just an empty one posted on that specific community with rewards declined and usually a link to the original in the body.