It's stopped by the fact that technically quantity that's being measured in the specific rules (http://prize.hutter1.net/hrules.htm) is size of the compression program plus the size of the compressed output ("zero-input decompressor" which is code+data that can produce the uncompressed output), so you can use static world-prior information but that counts against you twice as it has to be contained both in the "compressor" and the "decompressor".
For most cases the size of the "compressor" is irrelevantly tiny compared to the data, but if your "compressor" is a hard-coded pre-compressed file which it copies to the "decompressor" then the few percent of gains don't outweigh the fact that you've just doubled the size that's scored. It could be useful to include hardcoded priors iff they are very slow to compute but can be expressed in a small amount of storage.
For most cases the size of the "compressor" is irrelevantly tiny compared to the data, but if your "compressor" is a hard-coded pre-compressed file which it copies to the "decompressor" then the few percent of gains don't outweigh the fact that you've just doubled the size that's scored. It could be useful to include hardcoded priors iff they are very slow to compute but can be expressed in a small amount of storage.