Armory 0.93 on Testnet: consistent unconfirmed Txs sent from connected Bitcoin-cli (log attached)
OK, I solved this by numerous trial and error CMDs. The problem lay in the Armory implementation, specifically, the --datadir flag.

The working CLI flags:


ARMORY: -qt.exe --testnet --datadir=d:\data\armory\testnet3 --satoshi-datadir=d:\data\bitcoincore --rpcport=8332
BITCOIN-QT: bitcoin-qt.exe -datadir="d:\data\bitcoincore" -testnet -rpcport=8332 


Contradicting Armory's FAQ (in the FAQ itself) is the requirement to explicitly identify the testnet3 directory for the --data-dir flag (--data-dir==SOME\DIR\Armory\testnet3). If the testnet3 directory isn't identified, Armory confuses the mainnet blockchain data with the testnet chain data. 

The bitcoin.conf contents were:

listen=1
daemon=1
server=1
rpcconnect=127.0.0.1
rpcport=8332