You can do that, somewhat, by:
Creating an asset type of 'network cable' and give it a neat icon
Creating 24 assets of type 'network cable', for a 24 port switch
name each one accordingly (switchname_port1_cable) or something
edit the asset, add a relationship > is connected to > and add the switch asset for the target
make sure you can scan the switch by enabling SNMP and having the right credential - it will give you all the ports and descriptions that you put in the switch for port descriptions
Then, you can click the switch, and not only see whats on what port, but also the relationships to each network cable you associated with the switch - and the cable asset name you gave, will tell you the port.
That being said, I would never recommend doing that because to me the point of Lansweeper is to be dynamic inventory, and as we all know, cables get changed around, and all of the sudden your information is not accurate. I only trust dynamic data - which is why Lansweeper is so awesome.
I stick with port scanning of the switches - that's always accurate if you sweep it often - and I know what's on each port... then I have someone trace the cable from port 23 to the equipment I know its connected to... or reversely, if I know the server or device that's not communicating, I can say 'ok move the cable from port 12 to a free port, which I show there's a free one on port 22 - to troubleshoot things...