Pricing Attributes And Configurator

We are creating configuration models that will return between 50 and 150 lines to order managment.  In order to price the items in the configuration, we will be setting up multiple Pricing Attributes that are sourced from Configuration data.  For each product, we may need to source 10-20 attributes.  Between product models, many of the attributes will be the same...but each product will introduce a few new attributes required for proper pricing of the configuration.
In total, I estimate that we could be looking at a total of 150+ custom sourced pricing attributes.

Is 150+ custom sourced pricing attributes considered large in a typical implementation?  From my past experience, it seemed that all lines that are priced evaluate the entire set of pricing attributes -- even if they are not applicable and return no value.