figure the --rpcuser setting is not what I need, right?
That is correct, -rpcuser is completely unrelated to what you want to do.
You can start bitcoind with the -maxconnections=<n> option where is the maximum number of connections that you want to allow (or add the option to the bitcoin.conf file).
Then you can setup an external firewall to manage your connections. With that firewall, you allow through n-8-1 external connections on port 8333. This means that you are allowing other nodes to connect to you, but still keep one unused connection less than your maxconnections setting for your SPV wallet. Then you add another rule to the firewall to allow 1 connection on a different port which just forwards traffic to port 8333. You connect your SPV wallet to that other port.
That sounds good but could I have it even easier? If I set my bitcoind to listen on a non-standard port, it will not advertise this fact all over the place and keep all inbound connections available for me, wihtout having to config firewall?
With the firewall config it would obviously not know about the second port. Sounds easy, too. – Giszmo – 2017-10-25T18:40:59.930
1If you use a non-standard port, it will still be advertised and you will still get connections to it. You might get fewer connections, but there is no guarantee that using a non-standard port will ensure that you have at least one connection available for your SPV wallet. – Andrew Chow – 2017-10-25T18:42:26.867