The bug
When configuring debug settings for carvers, and setting the block's name to a block that updates with /setblock (see list in MC-31100), an acacia button is placed instead of the desired block.
In the screenshot attached, although I configured the settings with redstone wire, acacia buttons were placed instead.
[media]
How to reproduce
If these reproduction steps are more complicated than needed, sorry – I am not good with datapacks!
I was able to reproduce this issue by setting up a datapack using @unknown's example worldgen settings (here). I added "debug_mode": true, to the cave carver file under "debug_settings": {, and changed the default block placed to redstone wire (minecraft:redstone_wire) instead of crimson button. I then created a world using the datapack.
Could an example of a data pack that produces this issue be uploaded? The GitHub link is broken.
The default air, water, lava, and barrier states all fall back to the default air state (which I think is a separate bug), which is an acacia button. I imagine the issue here is that you're specifying an invalid block state, which falls back to the default value for the field rather than failing to parse the entire carver configuration.