The fastRedstoneDust setting breaks some basic circuits in 1.19, like the following 0-tick repeater:

This is due to the changes to neighbor updates introduced in 22w11a. Any shape and block updates emitted by redstone dust are now processed after the entire network has updated, rather than during it, as was intended.

While this can be easily fixed by calling the (now deprecated) BlockStateBase#neighborChanged method instead of the Level#neighborChanged method, that does introduce a way to bypass the max-chained-neighbor-updates server property.