In that case why dont you follow this procedure in order to define a bounty for whoever developer manages to code for Dash something similar to what you have just described?
1) Do you want the masternode software updates to be governed by a blockchain? (yes/no) (in case of a yes result, the 5 dash proposal fee is reimbursed)
2) In case of a yes in the proposal 1, do you agree to pay 50 dash to the one who will code it? (in case of a yes result, the 5 dash proposal fee is reimbursed)
3) In case of a yes in the proposal 2, do you agree to pay another 100 dash to the one who will code it? (in case of a yes result, the 5 dash proposal fee is reimbursed)
4) In case of a yes in the proposal 3, do you agree to pay another 200 dash to the one who will code it? (in case of a yes result, the 5 dash proposal fee is reimbursed)
e.t.c.
With this method, an amount of money will be allocated and given to the people that will finish the job. If nobody is interested to code it, then more money can be allocated, until the motivation is strong enough for the competent developers to start coding it.
If there is a no at the first proposal, this means that the masternodes dont like to decide about the updates, and that they blindly believe and trust to whatever the core team authority does.
Except that this code governance is just one of several core beliefs in the attributes of a long term stable crypto.. privacy-first is one of the other requirements and I'm currently making enquiring to analyse and uncover MNOs... well, they did vote for transparency-first...