Custom blocks with custom geometry has highly inconsistent redstone transmission.

 We've been trying to create custom blocks that interacts with redstone, with a custom geometry.

Part of a large redstone-based map.  If we use the unit_cube component and do not define a custom geometry, it works as expected.  

However, upon adding a custom geometry (unit_cube or not), the redstone transmission becomes consistently inconsistent. Upon placing down the block for the first time, the block does not register redstone powering it, or going through it.  However, upon reloading the world, the block that was placed now all of a sudden transmits redstone just fine. (Sidenote: getRedstonePower() in scripting also does not register the power. Only on world reload will it do so.)  

NB: We have included an addon and video so you can easily see & reproduce the issue in-game!  

Impact: This bug affects all of our custom geometry machines, which are the foundation of the map. Before approaching this solution we tried using functions to have a custom redstone detection, this is very performance intensive, and unviable for a marketplace map - it would undoubtedly be gray-listed.

Reproduce:
To reproduce: (all resources included in the addon above)

1) Create custom block with custom geometry
2) Create custom block with unit_cube
3) Load into world
4) Notice that custom geo block does not transmit redstone on first place
5) Notice that unit_cube block does transmit redstone on first place
6) Reload world
7) Notice that now custom geo block does transmit redstone

Observed Results:
Custom geometry blocks do not transmit redstone firstly upon being placed - only when reloading the world does it work.
Unit Cube does transmit redstone firstly upon being placed.

Expected Results.
Custom geometry blocks act as any other minecraft block in relation to transmitting redstone. And thus do transmit redstone upon first placement, without reloading the world.

Video of bug and addon included in attachments.