How is l10n/i18n generated "pod" going to work (how is the user going to care about it, experience it ... how will you package it )?

_generate_pod would not appear to belong inside App::ClusterSSH::Getopt ... how your project generates documentation is important stuff that should be documented (in pod) for you and other developers of this app of yours

I think its common to seperate code based on if its for-users-of-your modules and for-writers-of-your-module

How pod is generated doesn't sound like something users-of-your-module need to be cluttered with :)

I've seen a few distributions generate pod but they don't take l10n into account

So, Locale::Maketext way of organizing the localization data ( Handel::L10N::fr/Apache::MP3::L10N::fr ) sounds good ; esp if you avoid the pitfalls ( Rassie's Doghouse » On the state of i18n in Perl )

Generating pod sounds good ... be sure to add the headings  =head NAME to your i18n data

So I don't really see anything too messy ... it is what it is ;)