What about a time cycle - sharing of masternode role ?

We have a fixed number of 125  MN operating simultaneously.
Masternodes begin to operate and they take their MN ID and fill the queue order.
As the number of MNs is > 125 then cycling begins and MN ID #1 forfeit the role and goes to last position of the queue and MN ID #126
takes MN ID #125 and begin to participate (MN ID #127 takes pos. #126 and so on).
The cycling time can be let's say 6 to 72 hours so any of the MN candidates can estimate the exact time is needed
for taking the role (MN ID #128 -> 3 positions X 6 hours = 18 hours to take the role and 6 hours X 125 = 750 hours to forfeit it... and so on)
(*the cycling time can be fixed or variable -based on the MN candidates number-)

I think this approach has many benefits against ordinary established MN implementations.

I always believe that a master node must not be a privilege but a supporting=participation role with additional reward.

just my 2 cents...