Yes, that might help. I thought that a product could be like a CCK field in which you attach a price and SKU. I started designing something like that once but not in Drupal.

How would this affect product attributes? To say they should just be attached to the Node separately means you still have to track the SKUs of each. The main point of pain in UCs design seems to be that Products and Attributes are separate and the Product has to have 2 sets of behaviour depending on whether Attributes are present or not. I would think that one of the design goals of UC3 would be to simplify this into one Product behaviour.

Also, products as attachments to Nodes might make importing difficult as you'd need to specify Node ID(s) to attach the product info to?

So many balls to jungle with Drupal