Let there be meaning

[oshfdk]

Fully agreed. However, a one-to-many cipher would also break up such correspondences.

I think it's more like it could break up such correspondences. E.g., the following basic cipher from Vignère's Traicté des chiffres is a simple one table substitution cipher, that preserves all kinds of statistics from the text, however it has an alternative table that matches up letters with sequences of dots (or spaces of different widths, the author doesn't spell this out, but this cipher is described in the same section as pure distance/ruler based ciphers). So every 2-6 letters of the ciphertext one letter is encoded visually as a word break. Actual word breaks are not encoded at all. I showed the decoding process on this picture, I made it to make sure I fully understand myself this cipher in action. It's the general problem with old books on cryptography, they give a bit ambiguous description and then one example (with errors, usually) and leave it to the reader to figure out specific details. Trithemius was probably the trend-setter for this habit, or it was assumed that if a person cannot fill in the gaps, s/he has no business using ciphers anyway 

There are way too many quite different ciphers that could cause a mix of regular patterns and irregular overall structure like in VMS. I haven't yet found anything that statistically matches Voynichese, but so far no property of Voynichese that I'm aware of excludes a cipher of this general kind.

Full res of the image below is in this section of my text on distance based ciphers: You are not allowed to view links. Register or Login to view.

Also it's mentioned in this following section, where I talk about some properties of the text on f116v: You are not allowed to view links. Register or Login to view.

(I've noticed that GitHub doesn't behave well with section links when linking from an external page, like here. It would first scroll to the section header correctly, but then load the images and lose the location. Maybe tapping on a link, waiting for the page to load and tapping again can help with this, I'm not sure.)