This would be bad risk management. The random number makes it clear that not creating the fund wasn't an oversight, it was a willful deception.
Creating the possibility that some rotten luck could wreck you when you're most vulnerable is bad risk management. It's thumbing your nose in the face of Murphy's Law.
The only reason to do it this way is if there's no intent for the number to correspond to reality at all.
But to your point; if this code is written honestly, it's pretty weird that we don't see any code to post a transaction to the blockchain, or to verify that the funds are available to be allocated to the insurance funds. You would think that would happen before you wrote the new total to the database.
The RNG is used to give some variance to the number without accidentally making a pattern (which humans making up numbers tend to do). Literally using a RNG in code that’s meant to produce a value based on real world data is blatant and hard to defend if true.
...and if you are stealing, repeat a few digits occasionally: lack of repetition has caught several-a-tea leaf.
So technically it's not the randomness that's the issue, and a constant or manually updated fake amount would be as bad, but to me as a layman but it seems like they use a random number to imply a sophisticated risk management system.
It’s like putting pillows under your blanket so someone thinks you’re in bed. Once they find the pillows you aren’t going to get away with “oh I thought I was allowed to be out all night.”
When a software engineer writes code because the code makes sense or solves the problem, without interrogating the problem or how it applies to the real world, there can be real and significant consequences. We trust far too much of our lives to tech to ignore these issues when we're on the side of writing the code.
Seriously, that part is a humanities problem, and many engineers have little education in or understanding of humanitities (to the point of disdaining it).
If you study to do software engineering from the earliest age you can, do CS at university, don't join any clubs with others from non-STEM backgrounds, or even go to a STEM only university, then join a tech company big enough that you don't have to talk to non software engineers, you've just spent your life in a bubble. Sadly I think this is too easy to do.