Universal Offset is reverse of local offset (Which makes no sense). Local offset subtracts or adds to the map's offset. So if your map is timed correctly in the editor, when you go to play a +22 offset is applied locally (which shifts the map's offset to being later). This is wrong so when you use a negative offset around 20 it really shows the map is timed right but GG peppy and community offset. The reason why there is a community offset of 22ms is because the mp3 file peppy used for the offset wizard song has a 22ms gap in it from the start of the song to the beginning of the first blip. The offset in the editor for the song really should be +6ms not -6ms because the spike of the blip that will be most audible is 6ms after 22ms into the mp3 file.
Red - is the 22ms community offset that is applied
Orange - Where the offset should be which is at 28ms
Yellow - The offset should be 6ms in the editor because the +22ms (Red) is applied when you start the map.
Blue - Negative 6ms offset peppy has used in the editor for the song
Purple - What the offset is you are timing to in the options menu
Brown - Usually what the offset people think is correct (-3ms, -4ms, 5ms, etc). which means your offset really should be -9ms universally or more.
Maroon - What peppy was at and offset the map to, which he collected data and used to just set everyone 22ms off roughly.
What would work is correcting it in the editor to +6 and THEN using the options offset wizard and the song to check the offset. The offset wizard in the options has the community offset applied while using it (from what I've seen).
(I probably should have put arrows showing which way it's offsetting but you get the general idea.)
If I'm totally wrong, peppy please do explain. The offset is really giving me a headache.