The benefit would come if anything needs to be duplicated, the process would be faster. For instance, I mentioned XenFields may need to be replaced, we'll see if that's the case. If that ends up happening, I won't have to necessarily start from scratch since I already have custom fields developed into Classifieds.
If XenReviews still has a ton of bugs after XenGrid and XenFields are replaced and/or fixed then we may end up just scrapping it and starting from the Classifieds code base (I would obviously have to work out the details exactly with Stuart). If that happened, then obviously it'd help because XenReviews wouldn't be starting at 0. I do not intend on doing this at the moment, just entertaining your hypotheticals. Though it is worth mentioning this is the route that another (well respected in the community) developer has recommended for me to take today. It's something I'm open to but don't want to rush into. First I want to get widgets going and potentially replace XenFields. I think most of the components of XenReviews are fine (I'd also like to point out I was around for a lot of the development process of building that, after departing is when XenGrid, XenCashier, and XenFields were introduced and it appears they became the primary focus).