Your format (including /php.ini) was incorrect and I don't know why you got away with it for as long as you did. Perhaps the server hadn't been updated for a long time. Now, with that removed, are you sure that your reported error didn't change? Could it have been something now in php.ini, not .htaccess that was throwing an error? If the error is still reported to be in .htaccess, and your suPHP line is exactly as I showed you (with the correct account name, of course), then either you have something bogus in the WordPress stuff above it, or LP screwed up the upgrade/maintenance. You can try commenting out all the non-blank lines (with # ) in the WordPress section, and see if anything changes (your WP likely won't work right, now!). Offhand, I don't see any problems in the WP section, but it's possible that there's a subtle error. If that's not the problem, open a ticket, as it's something that LP needs to fix.
I'm assuming that you didn't make some silly editing error when adding or changing the suPHP_ConfigPath entry, perhaps leaving some invisible characters. For instance, using a word processor (like Word) to edit the file, instead of Notepad or some real editor. If it was working for some time before the maintenance, that's not likely the problem.
If the error has shifted to php.ini, your .htaccess is fine and we need to figure out what's broken in php.ini.