Adam, the problem with RE on the camera firmware is that it's much much larger and therefore very difficult to find a start and understand what's going on. It starts with the problem to not even know which part of the code would handle Wifi. OTOH, this Linux system is fairly well partitioned - each command has a name and it's comparatively easy to follow from the name to the code that handles it.
Additionally, what also makes hacking the card easier is that you can test "live", i.e. thanks to the Wifi connection, you can try things out and immediately see where it goes. The camera hardware, OTOH, is more a black box and much harder to give new software to run. That's why I wrote that I don't have the patience to help with the camera firmware. That could change if there would be some way to actually trace the code live, such as a JTAG connection, allowing to inspect and modify memory and code directly. But so far, it's just looking at tea leaves and trying to interpret what they mean
I mean, there doesn't even seem to be a hardware manual of the CPU available that could tell us what its capabilities and I/O ports are.
Also, I do not believe that the code is similar. The Flucard solution is a compromise due to the limitations of the card and its I/O ports. Duplicating that process in a system that doesn't require this card and a Linux system wouldn't be smart, and probably not making things easier for their developers, either.