Both are needed in half-duplex.
Duplex basically means: Two transmission channels, one for sending, one for receiving.
For Ethernet, full duplex means: TX and RX can happen at the same time.
For Ethernet, half duplex means: TX and RX do not happen at the same time, but still, being duplex, using separate channels.
This differs from the use of the word half duplex in other transmission schemes, like serial communications.
This has to do with the origins and definitions of Ethernet. Most of this goes back directly to what was possible 30 years ago, all 10base signals go back to 1981 at least. 100base was just an extension of that. Gigabit Ethernet changes this and does proper full duplex, sending and receiving on all lines simultaneously.
Now, speaking of oldstyle Ethernet, 10base2 etc: The protocols are hardware-independent. The same signal would be encoded on optical or electrical transmission channels. Back then, optical channels could not easily switch between sending and receiving. Also, early structured cabling Ethernet was connected on a hub (not switch), so CSMA-CD had to be implemented, meaning senders had to be able to listen for incoming transmissions (conflicts) during their own sending. And additionally, the early protocol stacks ran on CPUs so wimpy they could not calculate transmission and reception at the same time, giving you reason to drive half-duplex in an environment that was otherwise perfectly capable of full-duplex.
Half-duplex base-T Ethernet does not mean that the same wires are used for both directions of transmission, only that the two ends cannot transmit simultaneously.
Full-duplex means that both ends can transmit and receive at the same time, which only became possible with the shift from the shared coaxial cable to point-to-point unshielded twisted pair cabling.
There are never any physical collisions with base-T Ethernet, only "logical" collisions within a hub or switch. Even with Gigabit Ethernet, in which all four pairs are used in both directions simultaneously, each end uses a "digital hybrid" to separate incoming data from outgoing data on each pair.
Best Answer
Absolutely Yes. It won't be a bus as 10basex is, but will be point to point as most Ethernet implementations are today.
Read up on IEEE Std 802.3bw-2015 100BASE-T1 –Automotive Environment
This is a 100Mbps link over a single twisted pair.
You can also get out to 1000Mbps using IEEE Std 802.3bp-2016 1000BASE-T1 –Automotive and Industrial. Good for router powered ethernet based sensors.
This might be a good place to start, and it provides pointer to the newer SPE standards allowing both signal and POE over a single twisted pair.