I'm running a client on a computer within the company network and would like to access a server on my home network where I'm running the vpn server.
Home range: 192.168.1.X / 255.255.255.0 / Gateway: 192.168.1.1 / Server is running on 192.168.1.105
Company range 10.23.X.X / 255.255.254.0 / Gateway: 10.23.112.44

I've tried these steps:

Leave everything default: Connect -> Unable to get IP from dhcp server (Fair enough)
Change tcp/ip setting for virtual adapter on client. Set a fixed IP matching the home network (192.168.1.160) but do not set a gateway
-> Company network still works, unable to ping anything on home network
Same but add a gateway (tried both with 192.168.1.1 which is the actual gateway or 192.168.1.105 which is the vpn server)
-> Unable to ping anything in company network, unable to ping anything on home network

Switch ip settings back to dhcp on the client virtual adapter and enable secureNAT on the server with default settings and dhcp enabled.
Virtual host network interface settings on server: IP: 192.168.30.1 and the default dhcp range
-> When connecting the client gets assigned ip 192.168.30.10 and is unable to ping anything on the home network, but the company network works fine.

Added the default gateway for the SecureNAT settings to 192.168.30.1
-> Home network now works and I can ping 192.168.1.X ip's but the second I connect I lose connection to the company network.

This is where my networking knowledge ends and I'm stuck.
How do I enable settings so that the company network keeps functioning with its gateway and dns servers but also allows me to connect to ip's on the home network (ip only, no dns needed)

Set the server to use SecureNAT with Virtual DHCP. Under "options applied to clients" make sure that the default gateway, dns1, dns2, domain name boxes are all empty.

Click the button that says "edit the static routing table to push." In the box enter, 192.168.1.0/255.255.255.0/192.168.30.1

Now when you connect the client to the server you should get an IP address assigned in the range 192.168.30.0/24, and a route will be pushed from the server to the client machine, telling it how to route traffic that is destined for your home network (i.e. via the SecureNAT, assuming you've left it set on 192.168.30.1 as per your original post). It should not interfere with any existing entries in the routing table, so in theory all your company network stuff should carry on as normal.