In #41765 (closed) the custom home page was disabled due to a very low-security issue. However, this has created a number of complaints from users.
Thus this issue to implement a way to deal with both cases.
Options on the table are adding a setting/pref to restore old behavior, display a chrome banner with a string explaining why its not loaded, with a button to load it anyways; finally a combination of the two: add a setting/pref to restore the old behavior and display a chrome banner with a short explanation about why it is not loaded, as well as instructions for how to turn that behavior back on
I think asking them once via an inforbar and treating the user's decision as persistent is a nice solution! Maybe it should reset if the user's homepage is changed?
I'd be in favor of updating the wording so that the question of trust is more implicit, e.g.:
ℹ️ Tor Browser blocked your homepage (${domainName}) from loading to prevent it from recognizing your previous session [Load anyway][X]
Just because a home page can be malicious in regards to privacy does not mean the users should be enforced to use about:tor as the one and only home page. Personally, I find it quite unfair to be shown "Donate donate donate..." for more than 2 months because of a "bug" (and yes, I have donated, so it is annoying). If the Tor project is going to mistreat loyal users and supporters like this, maybe we should start having second thoughts.