Hi,
I would say that is a big form! 832 controls with conditional formatting sounds like a lot of work has been put into this. The C# code, 8,522 lines is a lot - I have seen more than that in an InfoPath form but that is still a lot of code.
The big question I have for you is performance: what (if any) performance issues are you experiencing with the form in SharePoint? SharePoint 2007 or 2010? How long does it take to publish that form and SharePoint doesn't time out?
Best practices would probably advise you to not design a form like this due to performance issues - but if it's working fine that's great.
For code we typically advise our customers to try to keep as much custom code out of their form as possible. We actually deveoped qRules (http://www.qdabra.com/en/products/qRules.aspx) for that reason. qRules has over 40 of the most popular code solutions for InfoPath but you don't have to write any code to use qRules - you just inject the DLL into your form (so it acts like a plug in basically) and call the code via rules. Without even looking at what your code does I would guess qRules probably does a lot of what your code does. If you are looking to reduce the amount of C# in your form you might want to see the feature set of qRules as it could help reduce your form size and help with any publishing issues you might have.
Ted