In some cases, getStateForPlacement overrides states that are saved on pickup, like lit state for furnaces, has_record state for jukeboxes or lit state for campfires.
The Problem here is that there's no real way for me to know if a state should be modified by the placement location, or it shouldn't. I could do primitive exceptions for direction and waterlogging, but that still wouldn't work for things like chests (sneaking placing single chest, not sneaking letting the chests combine to a double chest).
Since these states look like any other state, I can't say if I should use the updated state from getStateForPlacement or the one that got saved on pickup.

If anyone has any ideas on this, please let me know.

This has been fixed, or rather amended with the addition of a new config system. In versions 2.0.0 and up