looks like i was using pycoin wrong. for some reason the hex private key is not imported using a H:. the following works fine:
$ ku c4bbcb1fbec99d65bf59d85c8cb62ee2db963f0fe106f483d9afa73bd4e39a8a
input : c4bbcb1fbec99d65bf59d85c8cb62ee2db963f0fe106f483d9afa73bd4e39a8a
network : Bitcoin mainnet
You can use ku utility provided in pycoin library.
ku -s 0/0-2 xprv9xWkBDfyBXmZsA85GyWj9uYPyoQv826YAadKWMaaEosNrFBKgj2TqWuiWY3zuqxYGpHfv9cnGj5P7e8EskpzKL1Y8Gk9aX6QbryA5raK73p
will generate keys from index 0-2 on derivation path 0/x
a Bitcoin transaction can have between 1 and (realistically) several hundred inputs, each of which can redeem completely unrelated UTXOs. Whether or not the keys for those UTXOs are related through BIP32 or some other scheme is not relevant, and even not observable by the network (it is not possible to correlate different BIP32 keys unless you know their ...
A wallet service or application will not be watching all possible derivation paths. Yours at 0/77 is definitely not a standard derivation and you should not expect any wallet to pick up on transactions sent to addresses under that path.
answer is yes, its possible: I was merely doing it wrong in my earlier attempt(s):
have posted a gist to illustrate how I got it working using a few python libraries on the testnet: https://gist.github.com/kumrzz/111f8ea12af3528f496cbe678d153fc0