I strongly recommend making page length correction a Studio feature, not an XL feature. There are two reasons:
Having to use page length correction means the driver’s output is wrong. Page length correction allows the driver to function correctly in a studio environment without asking for fixes if the error is small enough (e.g., on the Epson ET-4850, a letter-sized page comes out 1 mm short, which might seem small but is pretty large by studio standards; uncorrected output (i.e., output from the Studio grade driver) is basically unusable in studios). Page length correction being an XL feature in effect means the user is being penalized for the driver’s bugs.
There’s no logical connection between page length correction and silkscreening. After the trial period, when the user needs to pay for a license key, the user turns to the website and the manual for clarifications about what silkscreening support means. In the manual silkscreen isn’t covered. On the web site, page length correction is not mentioned as a silkscreening feature. Existing documentation is misleading people to make the wrong decisions.