I've just made a quick test with neobuilder to check which encrypted addresses these bytes belong to and this is interesting:
0x006bc0 value is taken from encrypted offset 0
0x016bc0 value is taken from encrypted offset 1
the other two look less interesting, they are:
0x00ed41 value is taken from encrypted offset 0x18180
0x01ed41 value is taken from encrypted offset 0x18181
BUT, now things get more interesting
. by checking the decryption in ssv (not sp),
0x00ed41 value is taken from encrypted offset 0x0
0x01ed41 value is taken from encrypted offset 0x1
so, in summary, both SSVS and SSV dumps are wrong, the first 2 bytes of the V rom are wrong in both, unless they are patched by the decryption ASIC in some way, or offsets 0 and 1 have some other special xor value.
just to note which are the correct values:
in order to make the value at 0x60bc0 be 0x08, the encrypted value present at 0x00000 should be 0x43 (it is 0xE0)
in order to make the value at 0x160bc0 be 0x82, the encrypted value present at 0x00001 should be 0xC9 (it is 0x25)