1: No game can have a MC entry unless a guaranteed baseline of reviews are provided. This baseline should change based on the size of the game (i.e indies need less reviews, big AAA games need more) as well as its publisher (i.e a game from Devolver or NIS should have a lower entry requirement than a game from Microsoft, Nintendo, or SIE)
2: Outlet weight in the aggregate shouldn't be fixed; it should be based on the game being reviewed, the type of reviewer selected by the outlet to review the game, and whether the reviewing outlet's reviewer aligns with the goal of the game (i.e please hardcore fans only, please genre fans, expand the IP's appeal etc.)
3: Publishers need to specify what the goal of the game is market-wise. If it's mainly to please hardcore fans of the IP, then most of the reviews shouldn't focus or harp on the game not appealing to a larger audience. That clearly isn't what the game is aiming for.
4: Depending on the game's market goals, the distribution of review types should be accordingly set. The primary market goal can be one of the following: appeal to the hardcore fanbase of the IP (smallest niche), appeal to general core audience of the IP, appeal to fans of the specific genre type, modest expansion of IP appeal to non-IP fans, modest expansion of IP to non-genre fans, major expansion of IP appeal to non-genre fans (largest niche).
5: Every market goal should be paired with a creative goal of the game. Combination of market goal + creative goal should inform aggregate to determine the ratio of reviews for each of the market goals that are allowed. It's like a sliding scale, i.e if market goal = "appeal to hardcore fanbase of IP", then those reviews should make up the majority, while those that are of "major expansion of IP appeal to non-genre fans" should make up the smallest amount. Additionally, the former should have the most weight to the score, the latter the least weight.
6: After aggregate is informed of the market goal + creative goal of game and the scales/weights for review types are in place, review outlets can determine what particular review styles to submit that fit the desired bracket. Each outlet can submit multiple reviews if they want but only one per outlet is selected. Since the weight is determined by review type in relation to market + creative goal type set by publisher, an outlet's review's weight in the aggregate depends on what review type they submit and which review is actually approved.
This removes the built-in "system-gaming bias" that certain review outlets with fixed weights to the aggregate can utilize to manipulate review scores undeservedly positively or negatively.
7: To make things fair for review outlets, all qualified outlets receive review codes at the same time.
8: To curb unwarranted scores, all review outlets must have a fair mix of OBJECTIVE and SUBJECTIVE analysis in their reviews. The former can be measured against technical, performance, & mechanical standards (i.e visual resolution, framerate, geometry density, post-processing effects, frame pacing, foliage density etc.) as per the genre type (fighter, survival-horror, RPG, sim racer etc.), format type (traditional single-player, traditional co-op, PvE MP GAAS, PvP F2P etc.), and budget scale (indie, AA, AAA etc.). The latter can be measured against peer sentiment and related sentiment of similar games of that type (both for impact and consistency).
9: It should be the duty of the aggregate, with assistance from the publisher, to determine if reviews meet the Objective & Subjective requirements. This does NOT mean Objectivity & Subjectivity targets have to correlate with a high or low score, nor does this mean a review should be rejected simply on basis of providing a score a publisher feels is unfavorable.
10: A review outlet that feels their review has been unfairly rejected should have recourse to contest the objection of their review with a separate part of the aggregate that handles review disputes. If the outlet is found in the right, the aggregate must re-consider allowing the review into the aggregate. If the aggregate is found in the right, they are allowed to uphold the rejection of that review into the aggregate.
So yeah, basically that is my solution to the problem.