This is not needed. SegWit has been tested thoroughly. I don't see how an altcoin adopting and activating SegWit before Bitcoin does help SegWit activation in Bitcoin. Everybody with the slightest bit of technological understanding already knows that SegWit is a great step forward for Bitcoin in terms of capacity and security.
It helps because we could see and observe what the effects are in a real world setting and with a risk of potentially losing value. There is a difference in testing inside the testnet and outside of it because the problems go beyond the technical. If Charlie Lee intends to implement their own Lightning Network then the problems could be economical too since it will affect the miner's fees.
first of all.. litecoin is not used by 300,000+ merchants, so putting it on litecoin is not a comparison. the only reason litecoin was chosen is due to charlies brother bob. who is deep in the segwit rabbit hole (BTCC)
knowing that AFTER activation, MERCHANTS need to download yet another implementation that requires changing ALL the deposit addresses to new addresses should merchants want to utilise segwit, is not a quick endeavour.
litecoin wont cover that as its test as litecoin is not merchant heavy.
also the way litecoin mines blocks is not the same as bitcoin so thats not a comparison either.
the funny part is how the folk involved in core only spread their positive news and not the reality.
EG
https://bitcoincore.org/en/segwit_adoption/wheres the big names in merchants (that will do most transactions) coinbase/bitpay. hmm strangely not mentioned.
the hype that it has been thuroughly tested for months and they have been working with the whole industry. yet many are not even ready.
even funnier that even if ready. they end up needing to implement yet another version after activation just to get full wallet key utility.
but hey instead of releasing a version of core with dynamic blocks AND segwit. to give the community a real choice. they now want to waste time trying to get it activated on litecoin(for incompible/incomparable reasons). and then do a 'lets see what happens' and then later just push segwit back on bitcoin... surprisingly blaming one guy with 9% hash for why segwit is currently missing 75% hash.
i do find it funny that people say "everyone wants segwit". yet only 25% of pools do. and only 38% of nodes do..
core really need to make 2 releases..
0.13.1a segwit 1mb base 4mb weight(default fixed) <- the release already available
0.13.1b segwit 2mb base 4mb weight(default start with dynamic)
and then see what the community want. while still getting what they want
and stop this wait 2 years to see if segwit happens before proposing anything else, delay/stall tactics
lastly.. to add detail to BTCC (the main segwit pusher)
aswell as having a few sybil nodes running core to twist some numbers.
they are also running 54 of their own BTCC branded nodes
https://bitnodes.21.co/nodes/?q=/BTCC:0.13.1/... on AMAZON servers!!