If it has been more than a few hours since your last attempt, and the non-standard output you're trying to spend is still unspent,[...]
May be Sergio wants to create tx with non-standard output, not to redeem existing one?
[...] then there's probably a conflicting tx that spends the same output in the memory pool of Eligius, but it can never be confirmed because it does not have sufficient fees (Eligius requires 0.1mBTC minimum and 0.08192mBTC per 1KB).[...]
Wiki information is not up-to-date. I took this transaction
https://blockchain.info/ru/tx/225e8cf022bd8fe4c4b4f5aa11e1816c5bcd17dbcb1fd93894c0033778cc2acea week ago with standard 0.0001 fee (Eligius runs 0.8.x core). BTW, thanks to anonymous donater
[...]So unfortunately you're pretty much stuck until however long it takes for the transaction to "die off" from the memory pool. Could be weeks, or even months. There's no other major pool that will accept your non-standard tx.
1) There is no direct connection to Eligius pool node. 192.3.11.20 and [possibly] 68.168.105.168 are only gates to.
2) It is possible to check for current transactions on peer node. There is "mempool" packet in protocol
3) So, it is possible to check - was your transaction accepted by peer or not. I have such tool.
4) Unfortunately we have access only to a gates, not to pool itself. But if tx was not accepted to a gate node - it was not relayed to a pool node.