There are two methods I can think of, neither of which I would personally pursue.
1. Run the SQL Installation and when at the "Components to Install" screen, check "SQL Server Database Services", NOT including "Create a SQL Server failover cluster". You'll need disk that does NOT fail over, so if you're thinking of using disk that is already assigned to a CLUSTER instance, that will NOT be possible.
2. Run the SQL Installation and "Create a SQL Server failover cluster". You'll need cluster resources such as disk and IP. In this case, DO NOT make the other "NODES" available to this instance, therefore the SQL Instance will NOT "FAILOVER". I'm not too sure why you would want to do this, but it's possible. If you have the resources for the install, you might as well use the cluster for availability.
I would also add that #2 is similiar to having an existing cluster running then you have an issue with a NODE and need to EVICT it, so if you had a two node cluster and you evict one because you need to replace it, or for other reasons. In this case, you're down to 1 node until the 2nd node is added back in. Clusters are intended to keep systems up during server hardware failures.