I made the mod to the OPN cpu app and enabled those tasks again.
I actually just got one, but it will be days before it comes up in the cache to attempt to run.

WCG is all I am running, but I would have to suspend pages of MCM tasks in the cache to get Boinc to run the OPN task at the bottom.

It's not a beta task, it's a OPN cpu task due on 4/9.

I need to be more explicit it seems. My problem is not the possibility to modify a science application to make it run on a system it was not designed for, nor the possibility to replace it with a more efficient version. Also not data corruption. My problem is that apparently BOINC runs arbitrary code without any checks when you think there's effective measures to prevent just that. Is the idea of malware so absurd that nobody else thinks of it? BOINC has everything needed to notice when a file is not what is expected, yet it doesn't seem to check. I always thought it did, and wouldn't continue if there was any doubt. It seems I thought wrong.

Well, this is off topic here and has already become more lengthy than I intended with my quick remark. But my trust in BOINC has suffered and I hope I have raised some awareness even if most readers will call me a pessimist.

There is <verify_files_on_app_start/> in client_state.xml for rosetta at home, no wonder why it took like 10 seconds on every rosetta at home task to begin. But there isn't one enabled for world community grid. I didn't put that on, I believe the project owners can enable it from the server side config. I don't know which is better, faster task start, or slow and safer task start which can slow down computations calculating checksum/hash hundreds of times.

If app/program is compromised with malware, on Linux the permission is limited to "boinc" user so the possible damage is limited. Windows... not so good with permission stuff. BOINC Windows can install as service to limit permissions, but also limits to no GPU computations.
On linux debian: cd /var/lib/boinc-client/; su -s /bin/bash boinc
This is mainly just to test what the "boinc" user can or can not access. groups boinc shows boinc video render, so it have access to GPU computations as well.